What performance profiles actually change
No magic FPS numbers. A straight explanation of the settings FireClient ships, what each one affects, and where the gains realistically come from.
Search for any Minecraft launcher and you will find a number with a plus sign in front of it. We are not going to give you one. Frame rate depends on your CPU, your GPU, your render distance, your mod list and the world you are standing in. What a launcher can honestly do is stop wasting resources and make the trade-offs visible.
Memory is the first lever
Minecraft's garbage collector gets aggressive when the heap is tight, and long pauses show up as stutter. Too much heap is also a problem: bigger heaps mean longer collection pauses. FireClient's Balanced profile sizes the heap relative to your system memory and the mod count of the instance, and the slider shows the exact value in megabytes.
JVM flags, spelled out
- G1GC with tuned pause targets — reduces long collection stalls on modern JDKs.
- Explicit initial heap equal to maximum heap — avoids the runtime resizing the heap repeatedly.
- A small number of well-understood flags instead of a forty-flag cargo cult list.
Every flag in a profile is listed in the interface with its purpose. You can remove any of them, and the launcher will warn you if a value is invalid rather than launching a game that silently refuses to start.
What we will never claim
We will not promise a percentage increase, a guaranteed frame rate, or that a profile fixes a world that is simply too heavy for your hardware. What we will do is show you the settings, explain the mechanism, and let you measure the result in your own world.
A benchmark we publish is a benchmark you cannot reproduce. Measure it yourself.
Next post
The road to 1.0