Please update to 2.1.3 I think that latest issues with the read-only-db is solved there.
The monitor thread is just a thread that watches how much time is spent in GC, nothing to worry about. It would help us if you would detail your read operations in more details, i.e. code. Michael Am 26.08.2014 um 10:20 schrieb ashish jindal <ashishjin...@zophop.com>: > Hi Mattias, > I am using 2.1.2 embedded version. > I observed that in concurrent reads , threads waste a lot of time in > "monitor" state. So i tried EmbeddedReadOnlyDatabase by setting "read_only" = > true . But in the read only mode, the program ( a complete traversal of graph > ) becomes unresponsive, consuming all CPU. All 8 cores go to 100%. No > exception or error is thrown but only "not responding" . > > > On Thursday, July 3, 2014 2:34:04 PM UTC+5:30, Mattias Persson wrote: > Could you elaborate a bit on how you query? > > On another note I know that the upcoming 2.2 will aleviate a bunch of > contention points around transactions. > > Den 2 jul 2014 15:08 skrev "ashish jindal" <ashish...@zophop.com>: > Hi, > I am using neo4j embedded 2.1.2 . My use case is only read operations over a > graph database which i create once initially. Graph contains indexes over > nodes and relationships. Read operations include iterating over resources, > queries on indexes and graph traversals. > So the issue i am facing is : read operations seem inefficient over > multithreading. > e.g. > A read operation ( iterating over all nodes ) take about 300ms in single > thread but in multithreading it seems to wait until 1 thread is finished, so > 100 parallel threads take about 30 secs, which is as good as sequential . > This may be due to the way i am using transaction . I want to know what is > the best way to use transactions in my use case. > Can somebody help me out. > > Thanks, > Ashish > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to neo4j+un...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to neo4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
