On 1/5/07, David Abrahams <[EMAIL PROTECTED]> wrote:
[...]
Most of my content is static in nature, generated on-demand from ReST
sources. For those pages, the model checks the mod time of a
directory in the filesystem before deciding if the content in the
locmem cache is up-to-date.
Sorry but I don understand you here. Your content is static but
generated on-demand from ReST?
From what you have written your app is working like this:
1. your model checks the mdate of the (directory containing the)
ReST files and generating the (html?) content using the docutils
tools.
2. Then you cache the newly generated content.
But is that caching implemented by writing the content to a disk cache
(IMHO a recommended strategy in this case) or the locmem cache is the
only one you are using?.
If you are using only the locmem cache you could be dealing with
a scenario like this:
Since the locmem cache storage is non persistent and if you have
configured it so it the content is forgot after a certain period of
time this could be forcing the ReST -> html conversion to be redone
not only when you run the app/site for the first time but also after a period
of no use.
Have you measured how much time it takes a rst2html invocation with your
ReST documents?.
Sorry for making so many assumptions.
Another idea: If you are using locmem caching, could this be
consuming memory to the point of making your system start
swapping heavily and be the cause of the slowness?.
Regards,
--
Ramiro Morales
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
