Aleksandar Micic

This framework provides variability of object sizing and allocation rate: https://github.com/AdoptOpenJDK/openjdk-tests/tree/master/functional/SyntheticGCWorkload

we do the same thing in MM_ScavengerRootScanner::startProcessing ? we should probably rename it to be more specific like startContinuation(Objects?)Processing

Would could merge, but still the point is that startProcessing method needs a bit more specific name, about what kind of processing we start (in that merged case, for example...

we already have separate methods like: ``` MM_ScavengerRootClearer::scanContinuationObjects/scavengeContinuationObjects ```

Jenkins test sanity xLinux jdk19

jenkins compile win jdk19

> @amicic - By "while still obeying (-Xms, -Xmx) limits", do you mean that the new value should be greater than -Xms set value and lesser than -Xmx set value?...

I created https://github.com/eclipse-openj9/openj9-docs/pull/934 to cover missing docs (yet to be populated). We can close this issue now.

I'm not completely sure what docs this was referring to when talking about global GC points, but could be from here, when talking about gencon: https://www.eclipse.org/openj9/docs/xminf/ `For the gencon GC...

no direct/obvious connection, but it is a possibility (referring to my change)