f1racer328
New Member
From what I've read, ASP+ scripts are compiled and cached the first time they are requested. This speeds up processing since scripts aren't compiled everytime they are requested.<BR>But, if these compiled scripts are being cached in memory, doesn't this mean ASP+ is going to be incredibly memory intensive?Hi Leo,<BR><BR>This shouldn't have any additional RAM requirements. There are some memory issues with the bits made available at the PDC -- but these will be addressed with the final Beta1 bits. <BR><BR>We do not expect the memory requirements of ASP+ to be any different than ASP with the final release.<BR><BR>Thanks,<BR><BR>ScottThanks for the answer and I'm not trying to be a wise guy but I don't understand. <BR>What I'm thinking here: regular ASP doesn't have the code in memory until requested and once served, drops the copy; but ASP+ holds a copy after the first request, presumably until web services are stopped.<BR>So, how does IIS keep all these cached copies without requiring additional memory or are they written to disk or what have I missed here?Hi Leo,<BR><BR>We actually write the compiled code to disk and then memory map them in as DLLs. We will have the ability to drop infrequently used ones from disk as memory conditions become tight. We can then reload directly from disk (saving a parse and compile step) when they are next accessed.<BR><BR>- ScottRegular ASP *does* cache interpreted script code in memory - unless you've configured the app to run out of process and disabled ASP caching under "Process Options".<BR><BR>DuncThanks for the details, it makes more sense.