Strange HashLongSet behavior about koloboke HOT 3 OPEN

Given input is insufficient to investigate the problem. Please either share the data so that I could debug or run JVisualVM during that 5-8 min freeze, to see what actually is consuming time, to narrow the bug searching scope.

from koloboke.

I do understand that given input is insufficient. And I will try to get
more data but cannot promise that since it is actually happens on a an
environment which I have quite a limited access to.
Meanwhile I want to give you an input that such thing does happen maybe you
can think about something in code that might cause the issue.

2014-11-28 23:36 GMT-05:00 Roman Leventov [email protected]:

Given input is insufficient to investigate the problem. Please either
share the data so that I could debug or run JVisualVM during that 5-8 min
freeze, to see what actually is consuming time, to narrow the bug searching
scope.

—
Reply to this email directly or view it on GitHub
#32 (comment).

from koloboke.

Thanks for that. I reviewed the related code, and don't see what might cause such long pause. There are two potentially quite long (but still should be thousands times faster) operations: rehash and changing the free value (zero by default). If the items of the set ("followers") are always positive long values, you might try to construct the set using HashLongSets.getDefaultFactory().withKeysDomain(0, Long.MAX_VALUE).newUpdatableSet() and see what happens in this case.

If there is an issue with changing the free value or rehash, I would also note that this functionality is shared with all hash maps with long keys also. So using HashLongIntMap (for example) should also encounter "freeze". If you could check this it would be helpful.

from koloboke.