Hi all,

For the handbook application I realy realy realy need caching because
otherwise the application becomes very slow.

without caching a lot of processing and data-retrieval is needed: for
every item in the handbook all the alternative versions and their
meta-data need to be retrieved so that the most appropriate alternative
can be determined. This is necessary so that the correct title can be
displayed in the menu.
Since this is rather static content, going through the process of
building the whole menu on every page request is not very efficient.
I have done a test by caching the menu and all the alternatives on the
session and it has cut the time in 4 for a rather large (but not huge)
handbook.

Now I am looking for the best way to handle this caching, as I don't
have any experience with it.

would it maybe not be best to look at things like Memcached?
or would serializing the things I cache on the session for now and store
these in the database (doing just one db-query instead of a gazillion
and eliminating most of the processing) be a good solution?


I would appreciate your input!


Kind regards,

Nathalie


_______________________________________________
Dev mailing list
[email protected]
http://lists.chamilo.org/listinfo/dev

Reply via email to