Potentially useless allocations when checking a field cardinality
Hey folksIn a service running JanusGraph embedded, I observed a number of sizeable allocations coming from
JanusGraphVertexFeatures#getCardinalityFrom a profile (attached), it looks like
- A
StandardJanusGraphTx- The transaction will allocate a
CaffeineVertexCache- The
CaffeineVertexCacheNonBlockingHashMapI believe the sizeable allocations come from having batch loading enabled (making the initial
NonBlockingHashMapThat said, we could maybe disable the vertex cache by default when checking a vertex property's cardinality?
As in this change: https://github.com/JanusGraph/janusgraph/pull/4506/files
Happy to hear any feedback. Thanks!
