Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-10 Thread Michael Hunger
Guillaume, please try to reduce the memory mapped settings I provided, e.g by 30%. You can also inspect your system how much free memory is reported when you're running the neo4j test. This amount of memory can be added to the memory mapped file caches. Have you looked at the linux transaction

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-10 Thread Guillaume ALLEE
Hi Michael, I tried to lower the values by 30% = same and then by 50% = same again. (MapMemException) Here is the message.log http://pastebin.com/bvhhZfjZ My neo4j.properties looks like that : neostore.nodestore.db.mapped_memory=100M neostore.propertystore.db.arrays.mapped_memory=50M

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-10 Thread Peter Neubauer
Guillaume, you still having problems or is the performance ok now? I think with tweaking the 110 hops/ms can be upped to at least 500, since you are not touching any indexes except in the beginning. However, that would require to look at the underlying system and do some inspection. Let me know if

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-07 Thread Mattias Persson
Also, is that the first run directly after a JVM start? The first time you encounter a Node or Relationship it is loaded from disk into memory so that the next time it's read from memory instead. The difference between two runs can be order of magnitudes in difference. 2011/10/6 Michael Hunger

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-07 Thread Michael Hunger
It should, but in Guillaume's example they didn't differ by much, both were slow. It seems to be running with the default soft references cache which might turn over if every node and property is just visited once and then only a second time in the second run. Michael Am 07.10.2011 um 09:19

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-06 Thread Michael Hunger
How much memory does your machine have? What kind of disk is in there? Have you looked at the memory config for the neo4j db? What kind of scheduler do you use (please try deadline or as)? Can you please share the config and JVM info that is output at the head of graphdb/messages.log ? I'll

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-06 Thread Guillaume ALLEE
Hi, Here are the answers I can give you quickly: How much memory does your machine have? 5066 MB (from free -m) What kind of disk is in there? I do not know, the machine is a VM provided by another department of my company. What I can tell you is that on my i5 laptop the same was taking 6-8

Re: [Neo4j] Big Traverser perfomance : are '23 rels per milliseconds' good ?

2011-10-06 Thread Michael Hunger
Hmm virtual machines might be difficult, esp. with the io indirection. Your memory settings for the db are: • Fri Oct 07 00:10:01 IST 2011: neostore.nodestore.db.mapped_memory=20M • Fri Oct 07 00:10:01 IST 2011: neostore.propertystore.db.arrays.mapped_memory=130M • Fri