Re: [guilt] Taking too much CPU cycles
Re: [guilt] Taking too much CPU cycles
- Subject: Re: [guilt] Taking too much CPU cycles
- From: Erik Hanson <email@hidden>
- Date: Wed, 19 Nov 2003 14:58:33 -0800
On Nov 18, 2003, at 11:14 AM, Rob Kuilman wrote:
What do the programmers here do, to make their applications as
optimized as possible?
1. Determine performance goals (e.g., "should be able to de-colorize an
image file from a $300 consumer-level digital camera in less than 4
seconds on a 2 year old entry level Mac" or "should take up less than
$25 worth of RAM" or even "should get no speed complaints from 99% of
the users via a built-in feedback/bug reporting mechanism"). These
goals should be set by whomever you are writing your software for (your
boss, your client, your professor, yourself). Note that as time marches
on, the values will change (the image size of $300 digital cameras will
increase, but so will the processing power of a 2 year old Mac; RAM
prices will probably drop over time).
2. Write tests that verify those performance goals (and of course run
those tests often along with the rest of your test suite).
3. When a test fails, fix the performance, but just enough to get the
test passing again.
--
Erik Hanson
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.