Slidge: first beta of the 0.2 series — nicoco.fr
We have been way too shy with releases in the past, so we started tagging versions more aggressively. This has several advantages and there are no good reason why we did not do it earlier, really:
Since the latest blog post was about slidge v0.1.0, we will list (only) the major changes that we have achieved for v0.2.0beta0, some of which were actually part of the v0.1.1, v0.1.2 and v0.1.3 releases.
As planned, most of the work put into the 0.2.x series was about making slidge less RAM-hungry. There is definitely still room for improvement, but it looks like we have managed to avoid RAM usage growing constantly while running for several days, weeks or months; although I am unsure we have already reached the stage where it can run for months without needing a restart.
This was done by big refactors to ditch our hacky restart-persistent shelves for user registrations and avatar caching in favour of a proper SQL database. Then, more importantly for our matter, we could stop to store a bunch of python objects into RAM and spawn them only when needed from the data in our persistent storage, which is the right™ way of doing things.
