I thought I might move towards commit-option D (from my current default commit-option B)...
I notice that after the cache has been invalidated <optiond-refresh-rate> is 120 the NEXT operation is VERY VERY slow. i.e. Between invalidations the performance is good but when the cache is empty after having been flushed there is a pause on the next ejbLoad
3.2.2RC4 + Sybase 12
Well.. i decided to do a more extensive investigate and moved up to 3.2.3.
The problem doesn't exist in 3.2.3.
That's good news...
not sure why though... I looked at the source and couldn't see the issue.