yeah,this is a real problem in my scenario. The 100 concurrent threads is getProperty not setProperty.In my scenario I just sort a node list by node's property. And I found it is not fast in concurrent requests.Then I found these.
-- View this message in context: http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Has-been-blocked-when-i-get-the-node-s-property-tp3365819p3367782.html Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
