Hi! In some cases you could use annotations to hide transactions a bit:
http://wiki.neo4j.org/content/Spring_And_Neo4j http://wiki.neo4j.org/content/IMDB_Transaction_handling General information on transactions is found here: http://wiki.neo4j.org/content/Transactions If you describe your use case in more detail, others who did similar things could chime in with their experience! /anders On 05/24/2010 09:42 PM, Thomas Sant'ana wrote: > I've been doing some testing and study of Neo4J. I did a relatively large > load of my data set (which is small 5000 nodes). I was amazed on how fast he > load and traversal work (sure it's a small data set). Never the less we one > thing I noticed that closing transaction is pretty heavy. > > Each node object I store has 4K of data in 1 node with 3-5 related nodes. > Doing transaction for each node/relation is really bad on performance. > Having the entire object saved in one transaction is much better (but still > slow). Adding all objects in a single transaction is definitely the best > option (with my limited data set). > > The problem is that outside of the test it's strange to surface the Neo > transactions outside of the persistence layer. This is not really a neo > issue but since the difference is so large, I was wondering if there is a > nice way to do this? I understand that we can't nest transactions. > > What tricks can be used to hide the neo transaction needs from the rest of > the application and still allow certain control on that. Should I be looking > at JTA? Never used JTA... > > Thanks for any insight, > > Thomas > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
