Measure heap budget tradeoffs across three real client pairs
This commit is contained in:
@@ -42,6 +42,11 @@ collectors these can include cycle duration and overlapping phases; it is not a
|
||||
direct stop-the-world pause measurement. The viewer calls it collection time.
|
||||
Use [JFR pause events](profiling.md) when investigating GC-induced stalls.
|
||||
|
||||
The [three-pair heap experiment](heap-budget.md) compares 3 GiB and 1.5 GiB
|
||||
maximum heaps with the same core stack. It records variable RSS savings, nearly
|
||||
unchanged average FPS and increased GC accounting; playable defaults remain
|
||||
unchanged.
|
||||
|
||||
The native-read test exercises the real library, overlapping recordings,
|
||||
background execution, idle cancellation and unavailable-reader behavior on
|
||||
the build platform. This validates measurement availability, not an FPS or
|
||||
|
||||
Reference in New Issue
Block a user