Ahmed, could you please share some code?
Batch-Inserter should really only be used to insert millions or billions of nodes. With the normal API you can insert/update about 10k nodes/rels per transaction without any issues. You should be able to insert/update several thousand nodes per second into your graph and index per second. Everything else is not ok. The REST API is at least one magnitude slower than the normal Java API (probably even two magnitudes, depending on the types of operations). Michael Am 08.08.2011 um 15:04 schrieb ahmed.elsharkasy: > Yes i am inserting 3 nodes where for each node i search use batch index > whether this word is found in the graph to update or create another node and > this took 1 second which is too high for me > > another problem beside the time is that i have to open a transaction and i > use inside the transaction a batch inserter which made me open a graph > database service for the beginning of the transaction and then closing it > and starting my batch operations which i think is not good too.also the > shutting down of the service and starting the batch also swallows good bunch > of milliseconds > > Each node carry only 1 string property beside the id . > > Do you think this time is suitable ? from the rest api i used to insert more > than 50 nodes in less than a second > > By the way when i increased the number of inserted nodes to 500 , the time > is still 1 second , the problem is that i want to decrease this 1 sec to > half a second maybe or something like that > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Batch-find-tp3221634p3235486.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
