Paddy, posting on the user list - yes, I think you should add RAM to hold your graph in memory, and then maybe write some routing to warm up the caches. That is, read all nodes up into RAM before you do the first search, or e.g. perform some interesting searches to load all interesting data.
Would that be possible? What hardware config are you running on right now? Cheers, /peter neubauer COO and Sales, Neo Technology GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Sun, Jul 4, 2010 at 4:34 AM, Paddy <[email protected]> wrote: > hi peter, > Hope all is well, I have modeled the bus network with timetables and stops > connecting by walking distance. > There are approx 10 million and 1 million nodes. the graph is approx 1gb > Running on my local machine, to find the best route , it takes 5 seconds to > do approx 100 lucene query searches and add approx 100 relationships to the > graph > it can take from 3 - 10 seconds to find a shortest path , with the a star > algorithm. > > what steps could i take to speed up the app? More RAM? Run in the cloud? > Thanks > Paddy > > > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
