Background of the issue:
I was doing an optimization pass on my site and noticed an autoloaded field (wp_installer_settings) in the database that was a serialized PHP string, gzip compressed and encoded in base64, with a size of about 120kb.
Symptoms:
After decoding, I found it contained about 60 thousand characters related to the historic change-log of all WPML plugins and add-ons. This field is large and autoloaded, which affects performance. WordPress alerts users of autoload issues when the size reaches around 760kb. Reducing all that text to links towards a historic change log in the website would reduce the size of such field at least to 60 to 50kb and still provide the current information
Questions:
Can you implement a better way to provide the change-log data so it is not autoloaded in the whole site?
