I'm looking at the possibility of using GTop or Proc::ProcessTable to do the checking. There are some definite drawbacks, but it might still work to find largish memory leaks.

-sam

Oh, I dunno, it doesn't take that long. And unfortunately it's the only really effective way to see how much memory's currently in use, though even then there are some interesting bits to deal with.

Also, don't forget that Devel::Profiler is pure perl, and thus has a fair amount of overhead. Devel::Size is entirely in C, and a fair amount faster. I'd guess we'd see about a factor of 100 speedup over a perl version, but it might be upwards of 200 to 300 times faster for what it does, as well as immune to a lot of the problems you'd find doing this in perl. (It's not tripped up by tying or overloading, for example)

Gee, that sounds great! When can I use it? ;)

I'll be very interested to see just how fast it can walk every data structure in use by a large system like Bricolage. My gut reaction is still "a long time" but you clearly would know better than I!

-sam