- Why is Janusgraph's write performance above 1 sec per transaction?
Re: Why is Janusgraph's write performance above 1 sec per transaction?
toggle quoted messageShow quoted text
thank you for the response, it indeed helped for troubleshooting - the timings for one operation were in the order of 1-10ms..
Now I assume that the major drawback is inefficient queries of properties (string comparison). I will now implement indexing.
On Thursday, 6 June 2019 16:35:35 UTC+2, Florian Hockmann wrote:
Did you read other similar posts? Often the reasons are very simple for such a slow performance like no indices being used or because the queries need to be compiled first and you just measure a single request.
Here is for example a post that sounds similar to me:
It would be good to know in general whether you only measure a single request or perform like 1000 requests and compare their timings.
Am Donnerstag, 6. Juni 2019 16:04:39 UTC+2 schrieb Simon:
I have set up Janusgraph together with Cassandra + ES in the local server mode as described in the JanusGraph documentation
on linux red hat and interacting it with gremlin-python 3.3.3.
The configs used are (including start_rpc:true and cql as backend):
Invoke janusgraph via:
Interacting with the graph works well, but the slow performance struck me - one simple operation takes more than 1 second!
The operations look like:
Any clue how I can identify the reason for this slow operation?
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure. If you are not the intended
recipient, you must not copy this message or attachment or disclose the
contents to any other person. If you have received this transmission in error,
please notify the sender immediately and delete the message and any attachment
from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do
not accept liability for any omissions or errors in this message which may
arise as a result of E-Mail-transmission or for damages resulting from any
unauthorized changes of the content of this message and any attachment thereto.
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee
that this message is free of viruses and does not accept liability for any
damages caused by any virus transmitted therewith.
Click http://www.emdgroup.com/disclaimer to access the
German, French, Spanish and Portuguese versions of this disclaimer.
Join firstname.lastname@example.org to automatically receive all group messages.