memory-cache and disk-cache

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

René de Vries
<20 Posts

Posts:6

06/20/2007 6:45 AM
I'm looking for some practical advice on setting up the .config file. I've tried various settings, but so far I don't notice much difference. These are my current settings: memory-cache-interval="00:00:15:00" memory-size-limit="100" disk-cache-interval="00:00:15:00" disk-size-limit="1000" compression-algorithm="gzip" compression-level="high" And these are the relevant lines from the web.config My set up is a DNN 4.5 environment, which has about 30 pages (different TabId's). The individual pages are all dynamically build up (Using the Open Smart module). Basically, we're filling user controls with data that is generated using a stored procedure. So, this is the reason I've set up an interval for 15 minutes, as the database content CAN get updated every 15 minutes. What I am confused about it the relation between the memory-cache and the disk-cache. In my situation, wouldn't it be enough to just have a memory cache? What's the advantage? Any other tips on setting memory/disk cache? We migrated this site from a DNN3 environment. What I notice, is a much increased CPU time, and in general the response time seems slower. http://z.nu.nl is the public address. It's a dedicated webserver, and a dedicated database server. It should fly! Any insights appreciated. René

René de Vries
<20 Posts

Posts:6

06/20/2007 7:30 AM
We just removed pageblaster from the system. It was consuming many, many resources and I couldn't hold out any longer. CPU for the web process was running at 60% most of the time. I brought back standard DNN compression, and we're flying again. If anyone has an idea why this is, I'd like to know. One of our ambtions was building a validating DNN site, and pageblaster seemed very good at that too!

John Mitchell
Posts:3249

06/20/2007 11:25 AM
Hi René, One reason that PageBlaster may be using high amounts of CPU is because of a regular expression replacement rule that has run away back-tracking. This is a common thing with more complex regular expressions and just needs the rule to be "fixed" so that it doesn't do that. I have validated that all the rules delivered with PageBlaster do not use excessive CPU, but maybe you have some new ones that are causing this. Another thing that can happen is that the input to a replacement rule (the page source html) may have an adverse affect on the rule when applied. If you have any custom rules I would be glad to try them out and see if I can help narrow down the problem.

John Mitchell
Posts:3249

06/20/2007 11:27 AM
Oh, you also asked about Memory and Disk caching. You do not need to use disk caching, but it can help if you have a page that is not changed often and you want it to be available without having to be rebuilt from the database after an application restart. Think of the disk cache as a way for you to save a page as regular html that is always immediately available.

René de Vries
<20 Posts

Posts:6

06/20/2007 2:08 PM
Hi John, Thanks for the quick response. We used the standard rules, so no other processing took place.

John Mitchell
Posts:3249

06/20/2007 2:20 PM
It looks like a very high traffic site. Is it all running on one server? I could take a closer look if you wanted to send me your configuration offline. You can use the e-mail address in the readme file, or just respond directly to the notification from this post.

René de Vries
<20 Posts

Posts:6

06/20/2007 2:26 PM
Hi John, thanks for the quick response. It isn't all that high, we currenly serving some 30-40k pages per day. After the summer that will grow to some 100k per day. We've been running this kind of traffic on the DNN3 platform without a problem. Dual Pentium 4 webserver with 2Gb + seperate database server. High speed raptor disks. Now that DNN is back, I have less then 2% CPU utilization.

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.