[typo] Typo's memory footprint
steve.longdo at gmail.com
Tue Aug 8 02:37:38 EDT 2006
I posted a follow up showing some more specfic memory hogs. I haven't been
able to get anyone involved with RubyGems to clue me into why it needs so
much memory, yet. Anyone that reads this and can provide me some insight as
the runtime shenanigans of RubyGems please do leave a comment on my site or
feel free to send me an email directly mocking me :-)
On 8/7/06, Scott Laird <scott at sigkill.org> wrote:
> Thanks. Memory leak debugging with Rails is difficult.
> Unfortunately, slower leaks are even harder to find and harder to
> verify as fixed, but we'll find it and fix it.
> On 8/7/06, Steve Longdo <steve.longdo at gmail.com> wrote:
> > I've done a quick write up about this on my blog. I've also been doing
> > preliminary memory profiling. I'll be writing more about that soon.
> > --
> > Thanks,
> > -Steve
> > http://www.stevelongdo.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Typo-list