Maybe 'monitor' was too strong. I watched the size of the level 2 cache on the client as I retrieved vertices and edges in a controlled way and it grew by 1 each time I retrieved a vertex (well edge really b/c it would retrieve the vertex on the other side but that may only apply when using lightweight edges).
graph.getRawGraph().getLevel2Cache().getSize(); I currently turn off Level 1 and may disable Level 2 on my client soon anyway. According to the wiki, both caches are on the heap. https://github.com/orientechnologies/orientdb/wiki/Caching I think it's the read/write cache of the storage mechanism that can be off-heap and I'm not sure of the caching behavior here. https://github.com/orientechnologies/orientdb/wiki/Paginated-Local-Storage On Wednesday, April 2, 2014 3:00:36 PM UTC-4, cp2 wrote: > > > > This is where I may be confused -- I thought the caches were implemented > in 'direct memory': ie off-heap. > Off-heap caching is what I would want and expect to minimize work for the > GC, but is definitely not what I am seeing in the examples in my original > post. > How are you monitoring the cache? > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
