Jim,
 
I've seen these too (weird performance dips) on occasion as you describe. A couple of things i stumbled across in the last weeks ...
 
One is that for some reason, debug mode reports timings seem to be very inaccurate when using cfcs - in my quick tests, the more you employ during a request, the more inflated the reported timings become. Ben Edwards pointed this out to me when i asked about why the Mach II framework was taking so long. When i ran the same pages with debug mode off, using getTickCount() only around index.cfm - the reported timing was 5 times less! Maybe someone else has more accurate information on this descrepency.
 
The other is a very cool caching tag that Brandon Purcell posted on his site.
 
 
He states that you can get upwards of 700 pages a second under full load testing with this thing. And it's VERY simple to use. Surprise surprise - for once it came easy! Each page is cached individually as well, so you don't get a big hit that one user has to take.

Even then however there are odd weird performance dips: a method that takes 0ms 1,000 times will be reported as taking 60 seconds once.  There’s no specific load involved (in fact the machine is barely sweating) and no outward sign of trouble – but it just hangs (seemingly, I’m guessing waiting for some timeout someplace).

 

I’d like to track down why that’s happening… but it’s so inscrutable I doubt I’ll find it…  

Reply via email to