When you say publish to *static* cfm pages what do you mean. Doesn't cfcache accomplish this? Or does your content management system compile and publish the static cfm files on the Web site?
-----Original Message----- From: Matt Robertson [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 1:48 PM To: CF-Talk Subject: RE: MX Stability You can also throttle connections with IIS very effectively. In IIS properties for the web site, click the Performance tab. Check "enable bandwidth throttling" and be prepared to scale the speed WAY back. I had it down to 1 or 2 kbps once on a low-traffic site and no humans noticed any difference, but the SE hitting it with 850k reads per day was forced down to an acceptable level. This is one of the places where the benefits of using CF to publish to static HTML rather than assembling pages on request becomes really obvious. Wipes CF and your db out of the processing picture. A slight alteration on the same technique is to publish a *static* page with a .cfm extension. This will keep Application.cfm and OnRequestEnd.cfm still in the picture but eliminate all CF/DB processing in between. -------------------------------------------- Matt Robertson [EMAIL PROTECTED] MSB Designs, Inc. http://mysecretbase.com -------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
