Re: [infinispan-dev] DataContainer performance review
On 11-06-30 12:23 PM, Mircea Markus wrote:
> Yes, only 32 segments! Much of that performance impact in BCHM
comes
> from node tracking overhead per segment (queues, lists etc etc) as
> well. When we increase segment count this overhead falls
> substantially. CHM performs well with both 32 and 512 segments under
> these tests. It is just that BCHM basically grinds to a stop for
> large caches if we have 32 segments only.
Can't we adjust the segment size dynamically?
I don't think we can ignore
user settings for concurrency and max
capacity. Concurrency essentially equals to segment count. We can warn
user that if concurrency is inappropriate for container max capacity.