A public forum for discussing the design of software, from the user interface to the code architecture. Now closed.
With a classic ASP app I'm working on we've seen some good results by caching a few snippets of HTML generated from expensive db queries in the Application collection. It would be less than 5k of html at most.
Before we start going crazy with this approach are there any drawbacks or limits to the size of what we can store in the Application collection. Can we safely stick 500k of html in there? (5MB? 50MB?) Is the only cost losing 500k of RAM which is nothing really?
No luck finding info on this elsewhere, I thought there might be a few (ex) ASP gurus on here...
The application object has locking issues too. You might limit the ability of your site to effectively multitask.
Almost H. Anonymous
Wednesday, April 12, 2006
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz