Re: [Jruby-devel] Performance exploration

2006-06-02 Thread Charles O Nutter
I believe clean may be ok, unless there's a ton of WeakReferences getting collected. clean repeatedly polls the ReferenceQueue for any collected references, removing them from ObjectSpace. According to JavaDocs and the 1.5 ReferenceQueue implementation, each poll should just pull the 'head' item o

Re: [Jruby-devel] Performance exploration

2006-06-02 Thread Ola Bini
At 11:50 2006-06-02, you wrote: >On Fri, 02 Jun 2006 09:22:29 +0200, Ola Bini wrote: > > Regardig the ObjectSpace-implementation, I would recommend you to move the > > cleanup call to ObjectSpace#iterator() ... I think that's where most of > the > > performance go through the roof. > > And it's no

Re: [Jruby-devel] Performance exploration

2006-06-02 Thread Chris Nokleberg
On Fri, 02 Jun 2006 09:22:29 +0200, Ola Bini wrote: > Regardig the ObjectSpace-implementation, I would recommend you to move the > cleanup call to ObjectSpace#iterator() ... I think that's where most of the > performance go through the roof. > And it's not like those WeakReferences are a problem.

Re: [Jruby-devel] Performance exploration

2006-06-02 Thread Ola Bini
Hi, Regardig the ObjectSpace-implementation, I would recommend you to move the cleanup call to ObjectSpace#iterator() ... I think that's where most of the performance go through the roof. And it's not like those WeakReferences are a problem... /O At 07:54 2006-06-02, you wrote: >Scratch that t

Re: [Jruby-devel] Performance exploration

2006-06-02 Thread Charles O Nutter
FYI, the ObjectSpace performance hit appears to come from its use of a synchronized Set. If I modify it to use an unsynchronized Set, the numbers approach those when I have it completely disabled. Who says synchronization costs nothing? The ObjectSpace thing is particularly interesting since it wou

Re: [Jruby-devel] Performance exploration

2006-06-02 Thread Charles O Nutter
Scratch that thing about synchronization...I think my numbers got mixed up. It's still slow with an unsynchronized Set.On 6/2/06, Charles O Nutter < [EMAIL PROTECTED]> wrote:FYI, the ObjectSpace performance hit appears to come from its use of a synchronized Set. If I modify it to use an unsynchroni

[Jruby-devel] Performance exploration

2006-06-01 Thread Charles O Nutter
Some notes on performance exploration. Most of this is based on my belief that our core interpreter and the core native types (strings, symbols, fixnums, etc) are a large source of our performance woes. C Ruby is able to use extremely lightweight structs for most of these core types, and runs blazi