Is it the mod, or is it me?

Compare a run against machines like it. How cohorts and the index work →

Circinus writes a run id every time you record. Copy it from the Runs tab in game, or press Share there to open this page with the run already loaded. Hardware, mod count, game speed and result all come from the run, so nothing has to be typed and nothing can be mismatched.

Graphics is recorded for completeness rather than because it predicts anything. See the correlations at the foot of this page.

Millions of workload iterations per second, measured by the calibration benchmark rather than looked up from a specification. Two machines with the same processor and different cooling do not score the same.

Describe the run

Index 232 | | | machines
SIMULATION
54% of target
RENDER
59 fps of 60

Measured separately and against its own target. The simulation can stall while rendering stays smooth, and the reverse: they fail for different reasons.

Where this sits
▌ this run    ▌ cohort median   

What actually predicts tick rate
CPU single-thread index
strong  r=0.87
Installed RAM
weak    r=0.19
GPU tier
none    r=0.08

RimWorld's simulation is single-thread CPU bound. Players routinely blame the graphics card and buy the wrong upgrade. This is measured, not asserted. How this is computed →