TYPO3 Core

ModuleData of admin panel can be huge.

Especially the event module tends to have massive data, when this is enabled, and a non-cached page is called, it catapults the size of the HTML response from ~100k to 1,2MB - with a small page. Also, the cache_adminpanel_requestdata "cache" row is not ~200kb, but 16MB!

We need to revamp this mess and improve the data serialization plus the html creation side to be way more efficient, and to not go amok.

At the moment, I actually tend to at least disable the event sub module since it not only kills serverside parsetime, but browser rendering times easily, as well. Imho, we need to redesign the 'data storage' side api from scratch to prevent it from catapulting in size when anything but tiny object trees occur.

Also, the html rendering of the 'clicky' event tree is "not satisfiable" to put it mildly.