My guess would be that it’s the index updates that are taking time. It’s usually the case for any database that supports secondary indexes, that they trade write performance for read performance.
-- Chris Vest System Engineer, Neo Technology [ skype: mr.chrisvest, twitter: chvest ] > On 07 Dec 2014, at 07:25, Amit Kumar <[email protected]> wrote: > > Hello Experts, > > Need guidance on a critical issue I am facing. Using tinkerpop blueprints 2.5 > with community neo4j embedded mode, I am seeing gradual (very noticeable) > performance hit while inserting a bunch of vertices and edges (< 50 vertices > and 70 edges) in one iteration. The program is building vertices/edges based > on business logic. > > Have tried setting cache_type to none, and have indices on almost all > properties of vertices as well as edges with auto-indexer on. The first load > (on a clean database) takes < 1 second for < 100 vertices and < 120 edges. > Subsequent idempotent loads are getting slower by almost 800 milli seconds > (inconsistent). However, the time taken keeps increasing when the database > grows. > > NOTE: Program runs on a VM with data storage for the graph on CEPH. There is > NO fancy gremlin queries etc while trying to determine if a vertex/edge > already exists before inserting. > > Need quick help. Thanks in advance. > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <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.
