> I disagree, load testing comes after you have performance tuned the > application for single requests, the execution times will point you to > areas > of code that need improvement, or optimization, load testing can help > point > you to bottle necks exosed when the throughput is much higher than the > single request. Execution times will help you optimize the code, load > testing will help you optimize the logic. > I am sorry, but that is just not the case. Tuning based on a single request can negatively affect the performance of your application in the real world, which generally means more than one request at a time.
> That is entirely relative - if you are doing a query manipulating 40,000 > rows and your server is running on an old 486 with 64mb of ram then 250ms > would be pretty bloody quick (magic box quick!), and if you are displaying > a > simple "Hello World" template on an Athlon 1700XP with 2 gig of usable Ram > and a 3 gig Ram Disk containing your entire operating system, then 250ms > is > pretty slow. > It is not really relative. The user doesn't care what kind of server you have and how well the web application is working on it. The user cares about how quick the server responds. The 250ms number I through out is useful in the sense that it would be hard for a user to notice anything under that, but the user generally can tell if the response time is greater. Of course if your average page request is 100ms than you will likely be able to server more page requests than an average of 250ms. -Matt ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
