I'll take a stab. I really depends, on what you're doing.
I would say for most requests on a production level machine, it should fire off in 0 to 16ms, assuming the application and session were already initialized, and the template has already been compiled. It also assumes you have a vanilla page that just makes a request to a database and displays it. If you are doing something more complicated involving calls to a machine other than a database server (webservice, or FTP or pop) or IO, higher times are to be expected. I tend to trust the 250 ms that is set as the default debug warning time, for calls like these. And start to consider performance tuning at that point. I say consider because, maybe it's a call that a user will only make every once in a while (Say a preference change, or image process.) If that's the case, performance tuning might not be needed. However if your main page (the one users hit the most) is taking that long, you probably should performance tune. Hopefully this helps, or enough people think I'm wrong and give you better answers. Terrence Ryan Senior Systems Programmer Wharton Computing and Information Technology E-mail: [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:266894 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
