Last modified: 2014-05-05 12:42:58 UTC
This is to alleviate the issue raised by bug 46763, namely that ChangeNotificationJob runs out of memory when trying to load (hundreds of thousands of) Change objects from the database. A considerable amount of memory may be taken up by the diff contained in the Change object, especially if the change is not an atomic edit but a complex edit (from a bot, or a big undo, etc). To reduce the memory footprint, the diff should only be unserialized on demand, and the unserialized version should not be kept around (or only be kept in the Change object if this was explicitly requested, for speed). In addition, the (serialized) diff should be compressed (if larger than some constant minimum, refer to our memcached interface for reference).
Gah, where's the edit button?! That is supposed to be "hundreds *or* thousands" of Change objects.
(In reply to comment #1) > Gah, where's the edit button?! In https://bugzilla.mozilla.org/show_bug.cgi?id=40896
