Re: [Jruby-devel] Profiling work - memory

2006-07-09 Thread Thomas E Enebo
On Sat, 08 Jul 2006, Charles O Nutter defenestrated me: > >On 7/8/06, Thomas E Enebo <[EMAIL PROTECTED]> wrote: > >When I originally changed SourcePosition for RDT and jEdit > folks I had planned on leaving our impl at the single > SourcePosition > per line (that is all

Re: [Jruby-devel] Profiling work - memory

2006-07-08 Thread Charles O Nutter
On 7/8/06, Thomas E Enebo <[EMAIL PROTECTED]> wrote:   When I originally changed SourcePosition for RDT and jEditfolks I had planned on leaving our impl at the single SourcePositionper line (that is all Ruby cares about for a runtime).  After changingSourcePosition I thought of some ways to get the

Re: [Jruby-devel] Profiling work - memory

2006-07-08 Thread Thomas E Enebo
When I originally changed SourcePosition for RDT and jEdit folks I had planned on leaving our impl at the single SourcePosition per line (that is all Ruby cares about for a runtime). After changing SourcePosition I thought of some ways to get the memory usage much lower for SourcePosition (I wr

[Jruby-devel] Profiling work - memory

2006-07-08 Thread Charles O Nutter
This is an early snapshot from an ongoing gem run, same as the previous CPU profiling. At this point only 34MB of objects were live.This is with my ObjectSpace impl in place. I will run another profile without it to see how it changes. By method...- ObjectSpace is a BIG winner in the memory departm