Language pack script manipulates ORM cache

[Jeroen T. Vermeulen]

The language-pack export script currently still tries to manage and flush the ORM cache itself. Once we have the GenerationalCache in production, we can get rid of the complexity and rely on the ORM to get it right.

[Данило Шеган (danilo)]

If we are to do anything like that, we'd have to carefully monitor https://lpstats.canonical.com/graphs/LangpackRSS

Note that there are reports that new Storm causes more memory leaks, and brings staging to a crawl (i.e. staging itself uses 4GB of RAM now). So, this is something we need to keep a careful eye on.

[Stuart Bishop (stub)]

On Thu, Jul 2, 2009 at 6:09 PM, Данило Шеган<email address hidden> wrote:

> Note that there are reports that new Storm causes more memory leaks, and
> brings staging to a crawl (i.e. staging itself uses 4GB of RAM now). So,
> this is something we need to keep a careful eye on.

This is no longer the case. There are no known Storm leaks with the version used by lp:launchpad/db-devel

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/