make sure you are setting up your indexes. this was something that i did not do at first, but once i realized how important it was, my queries were incredibly fast. also, profile your queries by prepending "profile " to the query, and try to decrease _db_hits.
if you can provide the output of "profile ...", that would be awesome. On Monday, March 24, 2014 12:03:58 PM UTC-5, Rio Eduardo wrote: > > I'm testing my thesis which is about transforming from relational database > to graph database. After transforming from relational database to graph > database, I will test their own performance according to query response > time and throughput. In relational database, I use MySQL while in graph > database I use Neo4j for testing. I will have 3 Million more nodes and 6 > Million more relationships. But when I just added 60000 nodes, my Neo4j is > already dead. When I tried to return all 60000 nodes, it returned unknown. > I did the same to MySQL, I added 60000 records but it could return all > 60000 records. It's weird because it's against the papers I read that told > me graph database is faster than relational database So Why is Neo4j > slower(totally dead) in lower specification of pc/notebook while MySQL is > not? And What specification of pc/notebook do I should use to give the best > performance during testing with millions of nodes and relationships? > > Thank you. > -- 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.
