There is id reuse for production systems since 3.2.x In general if you don't use global scans ie no indexes your queries should not slow down.
Can you profile the critical generated cypher queries and see if they use indexes? Von meinem iPhone gesendet > Am 14.07.2017 um 14:30 schrieb Johannes <[email protected]>: > > Hi there, > we're running Neo4j 3.0.4 and also periodic integration tests in this graph. > > We observe that the tests get slower over time. These tests do excatly the > same actions on every run: Clear the graph (remove all nodes and relations), > add several dozen/hundred nodes with 3-5 properties each, and finally execute > some simple queries. Unfortunately, the execution time increases by some > seconds every time. > > I explained our whole setup in detail on Stackoverflow, but I assume the > somehow linear growth in execution time is a Neo4j issue and not due to our > software stack setup. This stack clearly adds overhead, but does not explain > the slowing. > Due to periodical node adds and removals, we observe a database growth as > well in neostore.nodestore similar files as described here. > > Assuming this is a Neo4j issue, is there any way to handle this database > slowing? Deleting/resetting Neo4j via "rm -rf data/graph.db" or using > store-utils are no options for our running system. Any help is appreciated! > -- > 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. -- 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.
