GC uBench: Difference between revisions

98 bytes removed ,  26 March 2015
v1
(checkpoint)
 
(v1)
 
Line 31: Line 31:
"Run All Tests" will do the same, but iterating through all loads. Note that each load will be run with its default settings. If you want nondefault settings, you'll need to run the tests one at a time.
"Run All Tests" will do the same, but iterating through all loads. Note that each load will be run with its default settings. If you want nondefault settings, you'll need to run the tests one at a time.


Finally, the oddly
Finally, the oddly named "Find Breaking Point" will attempt to search through the space of possible garbage-per-frame values to hit a specific target. Currently, it will try to find a setting that will hit 20fps 50% of the time. The resulting numbers are pretty unstable, but they should show large differences.
 
Notes to self:
# Instead of waiting for 1 second to start tracking fps, it should wait until the object piles are all replaced with the new settings' garbagePerFrame piles.
# Only! If frames are being skipped, then some larger piles will still exist, and they will dominate the garbage!
# So perhaps a full reset is needed, which wipes out all the piles and then waits for a cycle through?
Confirmed users
328

edits