Path: csiph.com!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: Lew Newsgroups: comp.lang.java.programmer Subject: Re: Good Fowler article on ORM Date: Sat, 12 May 2012 17:14:03 -0700 Organization: albasani.net Lines: 50 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net k4micNZZTKzielV829F6x0Sz372gWRF2ROc6FxAh1XIE89SwFhbNbjGI6XrY7lCm1e9YUjDFfq5WbU4jiJLRLQS3+NEE+eo0YRHR4424oD49yRje+Qw7bj2V6tEv7Ntc NNTP-Posting-Date: Sun, 13 May 2012 00:13:59 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="eiNducwxre1haTlU4ALG107kNUp/r2W6wpqY2KCTKU13JhG59T9kPEa68cnJmvGL6fEt6j4xx8ICuQqaBIQhyTvwN51KCLUrs8HsY4EzPF18e1AO3vgJQwE7d4Mq9LDn"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 In-Reply-To: Cancel-Lock: sha1:zzcknFDUAwAvIA0546X2xxO+Wf0= Xref: csiph.com comp.lang.java.programmer:14498 Jan Burse wrote: > Lew schrieb: >> You have yet to quote the statistics I requested. > > I didn't do some measurements, should be > clear from my response to markspace, isn't it? I responded to that post. The only facts you presented in evidence were that your Android times were slower by some unspecified margin than the desktop times, and that the Android platform was inherently physically slower than the desktop. I suggest that the platform differences, to which I alluded in some detail in that response, account for the performance differences you observe, or could. You need measurements that distinguish the effects of the platform from other effects to know for sure. At no point have you provided evidence here speaking to what in the environments could account for the difference, or apportioning impact to known factors such as the CPU speed and architecture differences. You probably don't actually know what causes what proportion of the observed (and undisclosed) difference. It is likely that the largest performance differences are due to the sorts of factors I mentioned in my other response. Why do I say "likely"? Because my own observations of Android applications and my knowledge of the platform and experience with the balance of attribute access via methods vs. other factors such as I/O, UI manipulation, thread foobars and the like, I have seen more performance impact from the platform effects than your suggested micro-optimization. But I don't know for sure. I haven't got your numbers. It is possible that you have evidence heretofore unshared that makes getters and setters the low-hanging fruit after all. So, naturally, I request that you share that evidence, at least in summary. Whatever your numbers do show, it makes sense to work first on the matters that make the biggest difference. If it's UI contention, work on that. If it really is class load, work on that. If it's logger crud, work on that. What you might wish to avoid is laboring intensely over an optimization that saves one part in a thousand of time, causes much more maintenance work due to workarounds and concomitant complexity induced by the fooferol, and is obsoleted in a year by platform advances. YMMV. But you might wish to educate yourself about where your actual problems lie. -- Lew Honi soit qui mal y pense. http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg