Hi Mwanju, As Mattias pointed out the idea is to pass around the instantiated NeoService to the different parts of the application that needs it. All Neo API operations are thread safe and just needs to be executed in a transaction (and you can have concurrent transactions running).
The startup and shutdown of Neo is not optimized at all and those operations are actually quite time consuming. Shutdown especially suffers a lot on the windows platform taking a lot of time because of issues with memory mapped regions to files. -Johan On Mon, Dec 15, 2008 at 1:19 PM, Mattias Persson <matt...@neotechnology.com> wrote: > Hi Mwanji, > > It's generally not desirable to shut down and start up neo instances > more than once in the lifecycle of a JVM instance. > ... > > 2008/12/14 Mwanji Ezana <mwa...@gmail.com>: >> Hello, >> >> I've been using Neo for a few days and am finding it interesting and useful. >> >> >> One thing I haven't seen mentioned yet is how expensive it is to start up >> and shut down Neo connections before and after each transaction. Should I >> minimise the number of separate transactions (I shut down after every >> transaction, to avoid any file locking exceptions), or are these operations >> cheap? _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
