Kjetil Kjernsmo wrote:
However, the content served will not change fast, so caching is going to be important. Also, the front page and the images on that page is going to be viewed far more than the pages underneath. So, I had this idea, how about caching the most requested files in the RAM, rather on the disc...? That would eliminate a quite significant bottleneck, wouldn't it?The first and most important step is to use a dual setup, with a lightweight apache proxy and a heavy modperl/axkit backend so that only the frontend gets to serve images and other such static stuff. You probably knew this already, but you never know :)
Based on that, I would recommend putting mod_mmap on your frontend. It ought to speed things up a lot.
Then, if you really want to speed up AxKit's caching, you could indeed start playing with caching stuff in RAM on the backend as well. You need to write your own AxCache module. I would think the best to do that would be to also use mmap (iirc there's a Cache::Cache module for that) so that all your AxKit daemons share the same copy (which ought to save memory).
IIRC benchmarks for cached content in AxKit show it at 80% of Apache's raw speed, which is very good.
--
Robin Berjon <[EMAIL PROTECTED]>
Research Engineer, Expway http://expway.fr/
7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
