An update: I have not tried your settings yet. But I changed the graph after reading your replies.
The evaluator was rejecting a lot of paths that were not of interest from the beginning. So I eliminated a relationship permanently from the graph (its benefits were limited) and other temporarily before traversing. It is cranking in the 500,000 end nodes range now. When I get around trying the config settings, I will let you know. Thanks! On Friday, August 29, 2014 10:31:22 AM UTC-6, José Cornado wrote: > > Hello! > > I have been running into the following problem lately (I swear that it > didn't happen before): > > I have a tool that lives inside an eclipse feature and the tool uses an > embedded instance of neo as its store. > > The data itself looks like a broom (several not only one) > > To retrieve nodes at the end of relationship X, I use evaluators. When > the number of these nodes reaches +80,000 the gc thrashes out. > > The amount of memory left seems sufficient (in excess of 20mb most of the > time) > > Is there an specific config property that I could tweak to lessen or solve > this problem? > > Thanks a lot! > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
