Open GoogleCodeExporter opened 9 years ago
The caching system for classes is intended to run in a multi-threaded, rather
than multi-process, WSGI setup. It was introduced because we observed
uncontrolled memory growth on previous versions of Python and SQLAlchemy, due
to object reference cycles which apparently were not detected by the Python
garbage collector.
However, after a quick testing of your patch, this memory problem does not seem
to arise on Python 2.7 (or at least, it is not as bad as in Python 2.6).
I will leave this issue open. While we perform some more tests, I would ask
you to observe how the NotreDAM memory usage varies over time in your setup.
Please report any anomaly. Thank you!
Original comment by alce...@crs4.it
on 18 Apr 2013 at 2:08
Original issue reported on code.google.com by
jonat...@metaltoad.com
on 17 Apr 2013 at 11:40