> > I wonder if I am in for some heartache as usage picks up. Or perhaps the > > better question is how many users will it take before I get the big performance hit. > > > It all depends on what your performance requirements are.
If all your "commonly hit" pages execute in under 100ms (through a combination of good code and caching), then having a few pages that take a looong time to execute may not cause any heartaches. For example, many systems use aggressive caching for the "public" side (taking into consideration "dynamic" pages), but won't use any cache for the administrative area, preferring instead for "live" views straight from the database. In a recent application, I had one particularly poorly written section of code that took maybe 8 seconds to run, but I knew it was only going to be hit by admins (they can wait) and only infrequently (once a week or so). I saw no need to optimize that piece of code, nor can I justifiably bill my client to speed it up. So, rules of thumb are great (I always strive for sub-200ms per page since most apps I build are not "high-traffic"), but they are just that. NAT ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
