Supernode problem is described (as an example) in this article : http://www.opencredo.com/blog/neo4j-super-nodes-and-indexed-relationships-part-i
Do gaedo suffer from such issues ?
Test that using Contiperf to provide effective measures.
The test should make sure that access time follows (at worse) a linear relationship with the relationship count.
If supernode is an issue for search (as it is for writing data) ... a radical solution should be found, no ? (hint : http://lists.neo4j.org/pipermail/user/2011-September/012362.html)
First test for #52.
This test does not expose the bug I'm chasing right now, but I'm sure it will expose it soon. However, it exposes another one : the inability of my implementation to have fully concurrent (read non-synchronized) code being run.
What to do to lower that sensitivity ?
To stand it clearly, yes gaedo is very sensitive to supernodes problems. And yesy this must be changed.
Hopefully, it will be changed bi fixing #68