This scenario has happened a few times... Stuff is serialized and de-serialized (to/from files) without problem. Code changes are made. At some later date, I notice that the Fuel file is orders of magnitude bigger than it used to be.

I usually manually de-serialize, and navigate the structures until I find the cause of the bloating.

Is there some package or code snippets that can quickly summarize the object classes and sizes in a serialized file, or from its in-memory de-serialized form?


Reply via email to