Github user ben-manes commented on the issue:
    Interesting. Then I guess the size must trigger the read bottleneck as 
larger than writes. Perhaps it is incurring a lot more GC overhead that causes 
more collections? The CLQ additions requires allocating a new queue node. That 
and the cache entry probably get promoted to old gen due to the high churn 
rate, causing everything to slow down. Probably isn't too interesting to 
investigate vs swapping libraries :)


Reply via email to