Hi guys. Indeed, this is something we wanted since a long time and it has already been discussed:�http://code.google.com/p/fuel/issues/detail?id=163
+1
I'd be very interested in that sort of thing.
On 02.11.2012, at 19:08, Yanni Chiu <yanni@rogers.com> wrote:
> 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?
>
>