Unless we're working with a small catalogue, or one with only a few popular items, I'm not sure we'd get much benefit from caching the XSLT-processed HTML for individual biblios. Outside of those cases, I don't think a lot of people will be looking at the same records, so we're just storing info until it expires, rather than reusing it.
Analysis of web traffic logs would indicate whether there are enough popular records in the OPAC for it to be worth caching. Perhaps we could do like the SilverStripe CMS does, and collect hit data, and build caches of anything that has a certain threshold...
-Ian
Check out redis too, very cool stuff.
ChrisFridolyn SOMERS <fridolyn.somers@gmail.com> wrote:Ok, thanks,
I have to learn more about memcached.2012/4/17 Robin Sheat <robin@catalyst.net.nz>
Fridolyn SOMERS schreef op ma 16-04-2012 om 16:13 [+0200]:
> But it would need a huge quantity of RAM no ?Not nearly as much as you would think, really. And it'll let the older
ones expire when things get full.
Also, if you don't mind gzipping it, it'll get quite tiny.
--
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
--
Fridolyn SOMERS
fridolyn.somers@gmail.com
Marsillargues - France
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/