Vanilla
Minecraft without Chlorine.
326.5FPS avg.
- Low
- 156 FPS
- High
- 486 FPS
Performance notes
Three setups. One early comparison.
FPS readings sampled from Minecraft recordings compare Vanilla, Chlorine by itself, and Chlorine alongside performance mods.
Test environment
Same machine. Recorded gameplay.
- CPU
- AMD Ryzen 5 5500
- GPU
- Radeon RX 6500 XT
- Memory
- 16 GB DDR4
- Render distance
- 12 chunks
Sampled FPS
A first look at the numbers.
Sampled FPS · not a full frame-time capture
Chlorine + performance mods
Chlorine alongside other optimization mods.
531.6FPS avg.
- Low
- 152 FPS
- High
- 1,162 FPS
Only Chlorine
Chlorine by itself.
333.6FPS avg.
- Low
- 284 FPS
- High
- 381 FPS
Average sampled FPS · bars share a 0–580 FPS scale.
How to read this
Promising signal. Not a final verdict.
Chlorine with performance mods had the highest sampled average: 531.6 FPS, about 63% above the Vanilla sample average. That result includes a 1,162 FPS reading from a particularly light scene, so it needs a controlled retest.
Only Chlorine averaged 333.6 FPS across its readable samples. These are sampled readings from the recordings, not a full frame-time analysis, so they don't establish that the other mods made performance slower.
About lows
Observed minimums aren't 1% lows.
A true 1% low requires frame-time data across the full run. A handful of visible FPS-counter readings cannot show frame pacing or reliably calculate 1% lows.
- Vanilla
- 156 FPS observed
- Chlorine + performance mods
- 152 FPS observed
- Only Chlorine
- 284 FPS sampled
Next: a controlled retest
Same route. Same settings. Frame times, not guesswork.
These recordings show different scenes and are not perfectly controlled. Repeating one route with identical settings and capturing frame times in CapFrameX would give a fairer comparison, including dependable averages, 1% lows, and frame pacing.