Frank Jacobsen wrote:
Faster = The fastest way this can be done.
If you really want "The fastest way this can be done", buy a better cpu. Then wait a few months, and there will be even BETTER hardware, so you can then that to get more speed...etc. Make sure you kill all other processes on whatever machine you are running so nothing else steals CPU time. If you are bound by disk reads, get a better disk drive. and so on...
What we're trying to get at is that this is not a spec. Something can always be done to make it faster. The question becomes "Is it worth it to make it faster than it is now?" and/or "how fast is fast enough?". If it can process each call in 10 microseconds, is it worth it to spend $1,000,000 to get it down to 9 microseconds? That would
be faster. Then do you spend another $2million to get it down to 8?
Best practices say you define what the speed needs to be before
you start optimizing. Then you look at where your bottlenecks are, what it would take to improve each, and at what cost. Then you decide which ones are worth the cost.
"The fastest way it can be done" is an unobtainable goal, as there is (for all intents and purposes) no end point.