On Thu, 13 Jul 2023 19:55:49 GMT, Aleksey Shipilev <sh...@openjdk.org> wrote:
> Realized that in production, we would like to see why trimmer might be late. > I think this would look even better: > [trimnative-shipilev-2.patch](https://github.com/openjdk/jdk/files/12043977/trimnative-shipilev-2.patch) I thought about this too, but you don't really want to know if it was suspended for every wait interval, but for every trim interval. In other words, you want to know how many trims had been moved up because a safepoint had been happening, and how many trims had been skipped due to pause. Getting these infos is harder than just increasing a counter. Is it worth the added complexity? ------------- PR Comment: https://git.openjdk.org/jdk/pull/14781#issuecomment-1635294737
