on 5/27/09 12:37 PM, Robert Brockway said: > Performance analysis can get very indepth. Once you resolve one > bottleneck another will appear but fixing them becomes a case of > diminishing returns.
Here's one rule I've learned -- the higher up in the layers you can make an optimization, the more you're likely to save. Fixing a problem in the application source code is likely to give you a lot more bang for your buck than trying to apply an optimization at a lower layer that lets you try to deal with the effluent coming out of the app. In other words, find and fix the real problem, and don't just try to put band-aids on the symptoms. -- Brad Knowles <[email protected]> LinkedIn Profile: <http://tinyurl.com/y8kpxu> _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
