You have to share more details. what versions do you use what is your stack what APIs do you use share the code to create the relationships what is getting slow how many concurrent users do you have
etc. Sometimes a slowdown is related to doing just one single update per transaction and having millions of those tiny transactions. So it makes sense to aggregate those changes into larger chunks, e.g. all create your knows relationships in one TX (and the other ones too). Perhaps something that might help you: http://maxdemarzi.com/2013/09/05/scaling-writes/ Michael Am 03.01.2014 um 14:09 schrieb Navrattan Yadav <navrattan.craterz...@gmail.com>: > Hi ... > Currently we have 1.5 million node and one relation : KNOW between them. > > > Basic Model is : when a user register we add KNOW relation to all his > friends. (friends are :phone book friends) > > Now its getting slow as user increase. so we want to add more relation > based on : COUNTRY, SOCIAL NETWORK, CITY, COLLEGE ETC. > > so we need to add these relation in existing node without blocking > database by running a separate thread. > > Please suggest some way,some query . how we can do this.... > > > > -- > 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/groups/opt_out. -- 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/groups/opt_out.
