Ryan Davis wrote:
> 
> On Feb 7, 2007, at 9:21 AM, Mark Alexander Friedgan wrote:
> 
>> We've been struggling with this problem for months. We use TupleSpace to
>> implement a distributed processing framework and periodically if the 
>> number
>> of objects
>> in the TupleBag gets large (not ridiculous but 50,000 or so) the 
>> TupleSpace
>> begins to take 100pct cpu and is effectively neutered and must be 
>> restarted.
>> We've been trying to come up
>> with a better implementation of TupleBag but have not had much luck so 
>> far.
>> Has anyone else done this?
> 
> What's happening is that you've populated a hash enough that you've 
> saturated the bins. You're now hitting a lot of hash collisions. 
Do Ruby's hashes not extend themselves once they hit a certain 
saturation?  Is there a hard limit at play here?  Or is it simply a 
matter of the hash function not distributing keys well?

-- 
Alex