Reduce memory footprint

[GoogleCodeExporter]

The current memory footprint is excessive, mainly because both the original 
summary text for a post is stored in memory, and also the text vector.

Original issue reported on code.google.com by lar...@gmail.com on 6 Feb 2011 at 8:33

[GoogleCodeExporter]

One way to do this might be to store the post contents in a dbm file where it 
can be looked up when we need to recalculate. In the meantime we don't need to 
store the contents, once the points have been calculated. The dbm file can be 
deleted and recreated every time we start the server.

Original comment by lar...@gmail.com on 13 Feb 2011 at 9:08

[GoogleCodeExporter]

The memory-save branch has made good progress on this. The original branch uses 
132 MB of RAM, but this branch uses only 53 MB. Stopping here to consider 
whether this is enough.

Original comment by lar...@gmail.com on 20 Feb 2011 at 3:41

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Not relevant any more.

Original comment by lar...@gmail.com on 20 Aug 2011 at 6:00

• Changed state: WontFix