Hi Marc, I tried rerunning the scaling test on a fresh graph with ids.block-size=10000000 , unfortunately I haven't seen any performance gain. I also tried ids.block-size=10000000 and

I am using janus client with hbase as storage backend. In my case, I am using index ind1 to fetch vertices from the graph. Upon fetching I am adding some properties (e.g one such property is p1) to

Hi, I enabled write-ahead logs to support index recovery for secondary persistence failures. I am trying to set TTL for write-ahead logs through JanusGraphManagement setting "log.tx.ttl". Tried below

Thank you Boxuan for the confirmation. I used the same approach of reopening graph as of now. It would be good if "logTransactions" can be refreshed on update of tx.log-tx by providing setter method

Well, the spec I am using is 32vCPU and 128GB memory. But I am testing Janusgraph with Cassandra as storage backend. I think this is not a thing with memory spec. I think maybe it is a thing with

Hi Radhika, Got it. You are right, you need to reopen the graph after setting `tx.log-tx`.

Hi Laura, You can only add a single level of metaproperties. One can understand this from the java docs.In a TinkerGraph a regular property is a TinkerVertexProperty with a property() method to add

Hi Laura, Using TinkerGraph I exported a graph to graphSON in the way shown above. I reloaded it as follows:So, the metaproperty added s read from graphSON. Do you mean to say that you cannot do the

Hi Shipeng, Did you use their machine specs: 32 vCPU and 244 GB memory? The graph is pretty big for in-memory use during OLAP: Best wishes, Marc

Just one more thing to rule out: did you set cpu.request and cpu.limit of the indexer containers to the same value? You want the pods to be really independent for this test.

How many "levels" of multilevel properties are supported by Janus? What I mean is, can I only add properties about other properties, or can I add an arbitrary number of multilevel properties, that is

Hi Marc, If you know how to handle MetricManager, that sounds fine. I was thinking in more basic terms: adding some log statements to you indexer java code. Regarding the id block allocation, some

Hi Marc, We're running on Kubernetes, and there's no cpu limitations on the indexer. Thanks for pointing this out, I actually haven't checked the overall resources of the cluster... It's a good

Hi Marc, Just to be sure: the indexers itself are not limited in the number of CPU they can grab? The 60 indexers run on the same machine? Or in independent cloud containers? If the indexers are not

Hi Boxuan, I can definitively try from the 0.6.0 pre release or master version, that's a good idea, I'll come back with the result, Thanks! Cheers, Marc

Hi, I didn't check your metrics but my first impression was this might be related to the internal thread pool. Can you try out the 0.6.0 pre-release version or master version? Remember to set

Hi all, We've been trying to scale horizontally Janusgraph to keep up with the data throughput, but we're reaching some limit in scaling. We've been trying different things to pinpoint the bottleneck

FWIW I've tried exporting the graph in the example to JSON (GraphSON) and the metaproperty *is* preserved, however when I import the same graph from the json file the metaproperty is not created.

Thank you for this example. After running this, I can see that the property "metatest" has been ignored and is missing completely from the GraphML output. Another issue that I have with GraphML is

Hi Laura, No. As the TinkerPop docs say: "graphML is a lossy format". You can try for yourself with:Best wishes, Marc