It's usually small; typically around 3 edges. Reading your article(https://li-boxuan.medium.com/janusgraph-deep-dive-part-3-speed-up-edge-queries-3b9eb5ba34f8). Outbound edges could be

When it takes over 3 seconds to return, how many edges does it return?

Hi All - I'm seeing a performance issue with this statement in Java code: Iterator<Edge> edgeIt = vert.edges(Direction.IN); in some cases this is taking over 3 seconds to return.  What can I do to

Thanks for all the help on this. I'm coming closer to a solution thanks to you all. Question - I've been using GraphTraversalSource to do all the adding vertices and edges to my graph.

Yeah using `newTransaction()` won't make a difference in your use case. Based on your input, there are a couple of things you could try: As suggested by Kevin, you could use locking. See

This from Titan, the predecessor to Janusgraph, but see https://groups.google.com/g/aureliusgraphs/c/z6kyGSlifXE/m/aLc2Zwb_BAAJ for some experience with a similar issue. You can either do locking and

So - unsurprisingly, Boxuan is correct. Code like this: GraphTraversalSource traversal = StaticInfo.getGraph().newTransaction().traversal(); try {

Good stuff - thank you Boxuan. Backend is Cassandra running on bare metal on 15 nodes. Race condition is rare. When the race condition happens, I'm seeing duplicate nodes/edges;

Hi Joe, Unfortunately the way Marc suggests won’t help with your usecase. Tbh I would have suggested the same answer as Marc before I saw your second post. If one has one JVM thread handling

Thank you Marc. I'm currently doing everything with a traversal, and then doing a traversal.tx().commit() Sounds like what you suggested is what I want, but just to be clear:

Hi Joe, Do you mean with threadsafe transactions that requests from different client threads should be handled independently, that is in different JanusGraph Transactions? In that case, I think you

Hi All - building a REST service using Quarkus to handle requests that operate on a graph. The current approach is: Static class that contains the JanusGraph and

Hi, We have created a Discord Server for JanusGraph to better support interactive conversations. So, if you would like to talk with other users and contributors of JanusGraph, then you can use

The JanusGraph Technical Steering Committee is excited to announce the release of JanusGraph 0.6.2. JanusGraph is an Apache TinkerPop enabled property graph database with support for a variety of

Great stuff! Is is really motivating to gain a much deeper understanding of the JanusGraph inner workings and get practical advice at the same time. Marc

I just wrote a blog post to explain the internals of edges in JanusGraph and give a few examples of how to optimize edge queries. Here is the medium blog post: JanusGraph Deep Dive (Part 3): Optimize

Hi Marc, Exactly suprised to see logs in stderr. Thanks, Nikita

Hi Nikita, Do you use the spark web UI? In the executor tab you can follow the stderr link and see any logged or printed output. No idea why they use stderr. Best wishes, Marc

Hi Senthilkumar, I remember the Gremlin.version() output of 1.2.1 in the gremlin console of the janusgraph distribution is a bug somewhere. You can look in the lib folder and see that janusgraph-0.6.1

Janusgraph latest version running on 1.2 version. But Gremlin latest version is 3.6. How to upgrade Germlin latest version? -- Senthilkumar