Glad I could help. 60 seconds is fine, though depending on the sites that run on the server and whether they deal with uploads and post- processing of user data, you can probably go with 30. If you have scheduled tasks or long-running queries in your code, you can always increase the timeout value for those individually.
Having the index page as a CFM shouldn't be a problem with a high number of concurrent requests as long as you have debugging turned off and set the production server variables in the CF Admin Caching section (i.e. Trusted Cache, Class Files, etc.). Having debugging (especially "Report Execution Times") on will kill your performance with any load. Jon On Nov 13, 2006, at 10:50 AM, PETER SHEATS wrote: > Hey Jon, thanks for the tip. I saw that it was indeed unchecked. > I set > it to 60 seconds, is that a good time? > > The site is www.pba.edu and it seems to be working now but very > slow. I > think the original problem was that our homepage is a .cfm page and > all > the University's computers' home pages are set to it so that's what > cause CF to crash. So I set that to an .html with a schedule task - > that might help some. > > I will indeed get one of those products - I think I did the trial of > Reactor but it ran out. > > Peter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260196 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
