It's possible that I haven't looked to hard, but my question is this:
A typical scenario for a site is to create a user. Before you create a user,
you do this in a transaction:
- begin transaction
- check if such a user (node in neo4j) exists
- if it exists, end transaction
-
Thank you for clarification!
Hi Dmitrii,
Separate threads can create nodes in different transactions, yes. You could
lock around the user creation code you included in order to keep user
creation atomic.
David
On Fri, Jul 16, 2010 at 10:59 AM, Dmitrii Dimandt dmitr
I'd like to introduce cali, another library to interface erlang and neo4j,
http://github.com/dmitriid/cali. The other one is nerlo,
http://github.com/nerlo/nerlo
Cali is an early version which is more of an experiment rather than anything
else, but it works. It's built on top of Gremlin, and
performance graph database.
http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party.
On Thu, Sep 2, 2010 at 4:18 PM, Dmitrii Dimandt dmit...@dmitriid.com wrote:
I'd like to introduce cali, another library to interface erlang and neo4j,
http://github.com/dmitriid/cali. The other
are), you can also
connect it to OrientDB and RDF SAIL.
Thanks,
Marko.
http://markorodriguez.com
On Sep 8, 2010, at 8:22 AM, Dmitrii Dimandt wrote:
cali has been updated slightly to become database-agnostic.
There are currently connectors to neo4j and TinkerGraph. It's now quite easy
I got cali's benchmark result. Well, sort of benchmarks:
http://github.com/dmitriid/cali/wiki/Benchmarks-of-sorts There's neo4j,
TinkerGraph and OrientDB
For some odd reason neo4j performs abysmally, though yesterday it was way, way
better: http://twitter.com/dmitriid/status/23912123904
Will
Yeah, I guess that could be a problem (or the problem).
Hmmm... I'll try and run the benchmark on a less busier machine and see what
happens then.
Thanks for the tip!
FWIW, I've noticed that neo4j seems to be fairly sensitive to disk I/O
performance.
I couldn't get it to work at all on
7 matches
Mail list logo
