On 20.06.12 23:51, Joseph A Calzaretta wrote:
> Are we doing something wrong? Is the behavior we're seeing intended or is it
> a bug? If it is by design, should it perhaps be documented somewhere that
> the performance of invalidateGroup is O(n) and not O(1)?
Obviously, the feature was not imp
Hello,
I couldn't find anything in the archives about this topic; please let us know
if our questions have been answered elsewhere.
We are using JCS 1.3 and have run into a problem with the performance of
JCS.invalidateGroup(String) when using an LRUMemoryCache. When there are
millions of obj