Hi, > So, using an embedded db is the only way to if you want one-shot deployment? > It might be worth it to see how difficult it would be to write that > component as a plugin to the build tool I use (Cake).
I'm not sure I follow. What's "one-shot" deployment? Deploying server is pretty trivial with modern automation tools. > I'd love to look at any resources showing performance comparisons between > server & embedded. Do you know of any? There have been some micro benchmarks on this list (Josh and Jake for example). Otherwise the performance of the server is pretty easy to reason about: Sp (q) = Ep (q) + Cn + Ct That is: Sp == server performance q == some query/database activity Ep == embedded performance Cn == cost of network (and serialisation) Ct == cost of transaction (since the server uses one transaction per request) You can approximate this as: Sp (q) = k + Ep (q) This applies to a single thread. Multi-threaded (i.e. multiple client) throughput will likely be lower on the server because it has to do extra work (the term "k" in the above) compared to embedded. You have to work out "k" for your system. It'll depend on file system, available RAM, how you allocate RAM to Neo, operating system... See: http://docs.neo4j.org/chunked/snapshot/configuration.html for information on how to configure your system optimally. Jim _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
