Re: Instiki with SQL backend

Alex Verhovsky
Wed, 17 Aug 2005 01:12:51 -0000

Tobias Luetke wrote:

>Go with caches_page for optimizing, then all you have to really worry
>about is searching. Thats going to be slow no matter what but at least
>its going to run against a practically idle database because all the
>other pages come from static files.
>
>
I hear you. Have a question though.

For the sake of searches, All Pages and especially RSS feeds. Why not
cache the raw markup, too, and do it in memory? If we only cache the
last revisions this way, even on something as [relatively] big as
rubyonrails.org we are probably talking about 2000 pages * 2 kb / page
=~ 4 Mb of RAM per FastCGI process. Even if I''m somehow off by an order
of magnitude, and it''s 40 Mb (for a rather huge wiki), it''s
still not
unreasonable for an active web site.

Alex