Django Lifecycle doubles memory usage of all "Content" objects due to change-tracking
Django Lifecycle has hook system that activates when fields on models are changed - in order to implement this, it keeps a copy of the initial state of all fields, so that it can tell when they change.
We do not benefit from this since content (at least, all content to date) are immutable, but we suffer significantly from it as it doubles the in-memory size of all content objects. When these objects are very large, as frequently occurs with the RPM plugin, this can be significant.
We should find a way to opt out of this functionality, or create one ourselves with an upstream contribution.
Please register to edit this issue