How much is too much information in memory? If memory was not an obejct, at what point would ColdFusion become unstable?
For example, if I load a query into a application scope variable that contains 200 records, and I use the query to build the navigation on my site each time a page is hit, will ColdFusion be able to handle the access to that data under load? -----Original Message----- From: Barney Boisvert [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 15, 2003 2:57 PM To: CF-Talk Subject: RE: MX Stability Another way to handle it is to cache content blocks (menu, page content, side bar, whatever), either in memory or the file system, and expire those caches as needed. Then your actual pages will dynamically assemble the pages from the cached content. Still a HUGE performance increase, but you maintain control over exactly what's cached. This is great for applications where certain pieces of all your pages MUST remain dynamic (like a shopping cart), but you don't want to have to hit the DB for stuff that doesn't change (like product listings). With a bit of additional work, you can even make user-specific caches for shopping carts and stuff. Beniot Hediard has a good application framework white paper here: http://www.benorama.com/coldfusion/index.htm It touches on a lot of topics, and while I don't like some of it, I'm a big fan of the pagelet/caching mechanism, and have built several caching systems based on what he lays out. cheers, barneyb --- Barney Boisvert, Senior Development Engineer AudienceCentral [EMAIL PROTECTED] voice : 360.756.8080 x12 fax : 360.647.5351 www.audiencecentral.com > -----Original Message----- > From: Matt Robertson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 15, 2003 11:43 AM > To: CF-Talk > Subject: RE: MX Stability > > > >Doesn't cfcache > >accomplish this? Or does your content management system compile and > publish > >the static cfm files on the Web site? > > The latter. The cms publishes a physical static page that has nothing > but html in it and a .cfm extension. This can be done versus a .html > extension for the simplest of reasons: so a user's session doesn't > expire. If you get fancy you can refine the process so that sections of > the page remain 'live' CF, thereby reducing the CF load but preserving > your ability to run code. It all depends on your app design, but either > way 'going static' will dramatically reduce server load. > > In this case cfcache may or may not be the right tool for the job. > You'd have to test it to see if shifting the load from CFPoint A to > CFPoint B solved the problem acceptably. > > -------------------------------------------- > 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4