Aye Nando... from what I've seen, simple code runs in anything from 0-31 milliseconds and really, even if it's 50MS, I don't care much.

50 thousandths of a second? Sheesh... it would take 50,000 locked simultaneous hits on the same code to cause the response to take one second... and a one-second response isn't bad at all. I rarely turn on debugging for anything except viewing SQL and/or variable data. I find the timing issues to be more a matter of distraction than of any practical value.

However, for things that are taking 5 or 10 seconds to finish (I had one that took 4 minutes to finish... but that was reasonable under the circumstances) it's nice to see where all the pieces fall into place and the trace with debug mode on is nice. It's only for very special situations where I find it useful for dealing with long-running code. Some application intialization processes can run to 90 seconds or more, so it's important to keep in mind where your long-running code IS, what it's doing, and what the user is experiencing at the time...

Load testing is important, too... performance under load is probably the most important because it tells us whether or not a long-running script runs longer, runs for the same length, or even (sometimes) runs faster when the system is under heavy use... and since we're all aiming for massive hit counts, it's really nice to have some knowledge of how many hits/minute your site can handle without bogging down. :)

Generally, the things that can cause performance issues are items like having a busy DB server behind it, slow connections to off-board systems (like web-services), or extensive generated content. This is where caching can become critical, because if you can cache pages that have LOTS of generated content it can really help keep your system's performance on an even keel.

Laterz,
J

On 5/15/05, Nando <[EMAIL PROTECTED]> wrote:
And from what i've heard, those reported timings aren't at all accurate - i think i remember someone said that CF has an accuracy of about +/- 16ms, so we see either 0, 16 or 31, and it means "roughly somewhere in there".
 
Honestly, i don't pay attention to them anymore. If a client says something about it being slow after i've done what i can on my end to a reasonable degree, i implement caching. :)




--
---------------
-------------------------------------
Buy SQLSurveyor!
http://www.web-relevant.com/sqlsurveyor
Never make your developers open Enterprise Manager again. ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm

An archive of the CFCDev list is available at www.mail-archive.com/[email protected]

Reply via email to