> RAM caching brings other issues to contend with, unfortunately. Canyou > keep everything in RAM, if you can't, what do you keep, do youcache page > components in RAM, are you willing/do you need to put upwith the overhead > of assembling components to render a new page, andso on.
RAM caching on typical Rails apps would be a little more nasty too. One FastCGI process caches a page, but the others don't know it's cached so they would have to regenerate it unless they all had some shared memory somewhere. Another question... wouldn't the buffer cache in the OS effectively work as a RAM cache if users frequently hit the same generated HTML file? That lets the OS take control of which pages are being more frequently used. Put in more physical RAM, more files gets cached, site runs faster without having to do any other work. I guess if you really wanted performance though and the total size of your static pages wasn't too great, you could always mount the public/articles directory over to a ramdisk... TX
