Once I redesigned the cache to have lots of Nodes with one value per node
(instead of a few cache nodes with lots of values) the persistence performance
improved dramatically. The data set size is around 100K entries;
using
1. file persistence my test run duration went down from 90 min to 2.5
Besides persistence, are there any other considerations in organizing the cache
as a small number of nodes with large number of entries per node, or with a
large number of nodes (and little data per node)? My initial assumption is that
Nodes are heavier-weight objects and, therefore, less is mor
We are using jboss cache(version: jbosscache-core-2.1.0.CR2, tree cache) within
a Java service. Our cache has very few nodes (around 3). Each of those nodes
can have lots of data (>100K entries). We are using BDB-J for cache
persistence, using the BDBJECacheLoader. Our data is non-transactional: