I knew this question was coming! :) Well, maybe you are right. The problem is that the function foo() involves much stuff, including disk I/O operations, so measuring its performance is quite tricky, you get different result on each test, depending on the available memory, disk busyness etc. It's hard to make a clean experiment. Generally, the foo() needs to be as fast as possible, because it is already long lasting. I have been optimizing foo() before, and now I need to make only a small change (choose x or y), and I am lazy to bother with profiling again, I just wanted to make the most optimal possible thing up front. Maybe it's just nit-picking... But I became curious if the above idea would be feasible at all!
Thanks Graham! On Mon, May 30, 2011 at 3:16 PM, Graham Cox <graham....@bigpond.com> wrote: > > On 30/05/2011, at 10:10 PM, Oleg Krupnov wrote: > >>> I am looking to optimize this code > > > Have you measured it and shown it to be a bottleneck, or are you just > assuming it will benefit? > > --Graham > > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
