Eric Hodel wrote:
···
On Feb 7, 2007, at 09:21, 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?I've heard a few people talk of it (mainly, TupleSpace with a
persistence (database)), but to my knowledge nobody's done it.
I observed a similar behaviour (incredible slow down with lots of entries). My
solution was to limit the number of entries to the TupleSpace by redesigning
the application.
Regards,
Michael