Memory and cpu for v3.1.5 to v3.2.0

[JonnyBhub]

Hi Ben,

We recently tried to update the cache version to 3.2.0 from 3.1.5 however has caused the production docker images to fall over due to CPU and memory spikes that weren't there in 3.1.5 and only since became an issue in 3.2.0. Have you observed this issue yourself or do you have a change in usage of the cache since 3.1.5 to optimize the access.

We are using spring boot 3.4.3 and deploying as a fargate instance

[ben-manes]

I am not aware of anything to explain that. The changes were bug fixes and the minor version bump was to add static factory convenience methods. I recommend capturing a JFR recording to pinpoint the activity causing high cpu.

jcmd "$(pidof java)" JFR.start duration=180s filename=/tmp/app.jfr settings=profile.jfc

[JonnyBhub]

Thanks for this Ben, I did some extensive testing on all the dependencies and found the issue wasn't related to this, apologies.

Are you able to explain how you have seen the performance gains from the cache filling up? I would have thought the time it takes api calls to get the data that fills the cache would have remained the same but I did see an speed increase of about 3x from 3.1.5 to 3.2.0

[ben-manes]

The only optimization that I recall is #1320 which would cause some updates to not unnecessarily overwhelm the internal write buffer and cause writing to be throttled so that eviction can keep up.