I've never seen or heard of any such issue.
Sent from my iPhone
> On Nov 23, 2015, at 01:27, Mr. W wrote:
>
> I heard it from Russian devs and I'm really worry about. I don't think they
> aren't experienced. Anyway I need to be sure I'm doing good choosing neo.
>
I have never seen such a thing and I don't know what they actually mean.
Perhaps you can ask them to clarify and prove code and measurements.
If you check neo4j.com/customers you'll see you are in good company
Von meinem iPhone gesendet
> Am 23.11.2015 um 07:27 schrieb Mr. W
I heard it from Russian devs and I'm really worry about. I don't think they
aren't experienced. Anyway I need to be sure I'm doing good choosing neo. They
said that when number of relations grows then delay between what you update and
what you read is more noticeable.
--
You received this
Not sure who told you that. And I don't really understand what you mean.
Neo4j has no delays, after you commit your update it is available to all
readers immediately.
Michael
> Am 22.11.2015 um 19:09 schrieb Mr. W :
>
> Hi guys,
>
> I started to use Neo4j in
Hi guys,
I started to use Neo4j in production. But somebody told me that neo4j has
big delays when you have more data and you're selecting after saving on
existing relation (propagation). Especially on relationship's properties.
Is it true? Is there any case where delays occurs and how long