What are 1% lows and 0.1% lows?

When players talk about performance, they usually mention average FPS.

“I get 140 FPS.”

“After optimization, I got 170 FPS.”

“Rust holds around 120 FPS.”

At first, that seems enough. But in real gameplay, average FPS can be misleading. It shows the general picture, but it does not show how badly the game behaves during its heaviest moments.

And those moments are usually what the player feels the most.

You can play with good average FPS and still get stutters, sharp drops and the feeling that the game is not smooth. This is especially common in Rust, CS2, Tarkov or Warzone, where system load can change in a second.

This is where 1% lows and 0.1% lows matter.

These metrics help you understand not just “how much FPS you get on average,” but how stable the game is when the system is under pressure.

Why average FPS is not enough

Imagine two situations.

The first PC shows:

• Average FPS: 150
• 1% lows: 55

The second PC shows:

• Average FPS: 125
• 1% lows: 105

If you only look at average FPS, the first PC looks better. 150 is higher than 125.

But in real gameplay, the second one will almost certainly feel smoother. Because it has fewer sharp drops. It does not just show nice numbers in easy moments — it holds up better when the load increases.

• Average FPS is like average speed during a drive. If a car goes fast but suddenly brakes every few minutes, the trip still feels bad.

Games work the same way.

Players do not feel the average number. They feel the drops.

What 1% lows mean in simple words

• 1% lows show how low FPS drops during the worst 1% of gameplay moments.

It is not the absolute lowest FPS number ever recorded. It is a more useful way to show bad performance moments.

For example, if a game shows 140 FPS on average, but 1% lows are around 60 FPS, it means the system drops quite hard during heavy scenes.

These drops can feel like:

• micro-stutters
• choppy image
• sudden loss of smoothness
• strange mouse feeling
• delayed response

instability during fights.

• 1% lows reveal what average FPS hides.

What 0.1% lows mean

• 0.1% lows are an even stricter metric.

They show the worst, sharpest and most unpleasant drops.

If 1% lows describe heavy moments in general, 0.1% lows show the most extreme instability spikes.

For example:

• Average FPS: 150
• 1% lows: 95
• 0.1% lows: 35

At first, the game looks fine: average FPS is high and 1% lows are not bad. But if 0.1% lows drop to 35 FPS, it may mean that the game sometimes has harsh freezes.

Those are the moments players remember.

Not “I had 150 FPS.”

But “my game froze when I started shooting.”

Why 1% lows matter more than maximum FPS

Maximum FPS says very little about real gameplay.

If the game shows 240 FPS once in an empty area, it does not mean it will perform well in real conditions.

This is especially true in Rust.

You can stand in a forest and see a beautiful number. Then you enter a large base, meet players, see many objects and effects — and FPS suddenly drops.

Maximum FPS shows what the system can do in an easy moment.

• 1% lows show how well the system holds up in a hard moment.

For the player, the second one matters much more.

Because fights, loading, fast camera turns and complex scenes do not happen in perfect conditions.

Why drops feel so noticeable

The human brain quickly gets used to smoothness.

If you are playing at 140 FPS, after a few minutes that becomes normal. But if the game suddenly drops to 70 FPS for a short moment, you feel it.

Not because 70 FPS is always bad. But because the change is sudden.

The game breaks the rhythm.

This is especially frustrating when the drop happens during an important moment:

• you start shooting
• you turn the camera quickly
• you enter a base
• another player appears nearby
• the game loads objects
• an explosion or effect happens
• you open inventory

the system starts a background task.

That is why stability often matters more than the highest number.

• 1% lows and frame time are connected

To understand 1% lows, it helps to understand frame time.

FPS shows how many frames the system produces per second.

Frame time shows how long each individual frame takes.

If frames arrive evenly, the game feels smooth.

For example:

8 ms, 8 ms, 8 ms, 9 ms, 8 ms

That is good.

But if frames arrive like this:

8 ms, 8 ms, 42 ms, 9 ms, 8 ms

One frame takes much longer than the others. The player sees it as a hitch.

When these hitches happen often, 1% lows and 0.1% lows drop.

So bad 1% lows often mean unstable frame time.

Why Rust is especially sensitive to 1% lows

Rust is a game where average FPS can look fine, but the experience can still feel bad.

The reason is that Rust constantly changes system load.

Performance can be affected by:

• large bases
• number of objects
• nearby players
• world loading
• effects
• sounds
• lighting
• inventory
• memory usage
• CPU load

Windows background processes.

That is why in Rust, it is not enough to know how much FPS you get on an empty map. What matters is what happens during heavy moments.

If average FPS is high but 1% lows are low, the game will feel unstable.

For Rust, this is critical because one stutter can decide a fight.

Good and bad 1% lows

There are no universal perfect numbers because everything depends on the game, monitor, settings and hardware.

But the logic is simple:

If average FPS is high and 1% lows are much lower, there is instability.

For example:

• Average FPS: 160
• 1% lows: 140

This is excellent. The game should feel smooth.

• Average FPS: 160
• 1% lows: 90

This is a noticeable drop, but it can still be acceptable in a heavy game.

• Average FPS: 160
• 1% lows: 45

This is bad. The player will probably feel stutters.

The value itself matters, but the gap between average FPS and 1% lows matters even more.

The smaller the gap, the more stable the game feels.

Why optimizers often show only average FPS

Because average FPS is easier to sell.

The phrase “we increased FPS from 110 to 145” looks good. It is easy to put on a landing page, an ad or a video.

But it does not always show the real result.

If after optimization:

• Average FPS increases,

but 1% lows stay bad,

and stutters remain,

the player may barely feel the improvement.

But if average FPS increases only a little while 1% lows improve a lot, the game can feel much better.

That is why honest optimization should not look only at average FPS.

How PulzeOS looks at 1% lows

PulzeOS is not built only around the idea of “more FPS at any cost.”

The more important goal is stability.

PulzeOS tries to create a cleaner gaming environment where the game faces fewer random background processes, less system noise and less unnecessary load.

This can help in the moments where normal Windows becomes unpredictable.

The idea is not just to show a better number in the corner of the screen. The idea is to reduce how often the game falls apart during heavy situations.

If 1% lows become higher and frame time becomes smoother, the player often feels that more than just an extra 10 FPS on average.

Why 0.1% lows are hard to improve

• 0.1% lows often depend on the sharpest and rarest problems.

This can be caused by:

• sudden file loading
• system process activity
• antivirus scan
• CPU spike
• object loading
• driver issue
• not enough RAM
• disk access
• overheating

overlay conflicts.

That is why 0.1% lows are harder to stabilize than average FPS.

But they are often responsible for the most annoying freezes.

PulzeOS cannot guarantee that it will remove all of these spikes on every PC. But a cleaner and more predictable gaming environment can reduce the number of factors that cause them.

How players should measure performance

If you want to understand how well a game runs, do not look only at the FPS counter.

It is better to look at:

• average FPS
• 1% lows
• 0.1% lows
• frame time graph
• input lag by feel
• stability in real gameplay scenes

behavior during fights, bases and loading moments.

The most honest test is not standing on an empty map and looking at a number. It is testing the game in the conditions where it usually lags.

For Rust, that can be a large base, an active server, a fight, world loading or a place with many objects.

The main idea

• 1% lows and 0.1% lows exist to show real game stability.
• Average FPS shows how fast the game is on average.
• 1% lows show how stable it is during heavy moments.
• 0.1% lows show the sharpest and most unpleasant drops.

If you want to understand why a game stutters even with good FPS, these are usually the numbers to look at.

Final thoughts

• 1% lows and 0.1% lows are some of the most important metrics for understanding real gaming experience.

They do not show a beautiful average number. They show how the game behaves during bad moments.

For games like Rust, this is especially important because stability often matters more than maximum FPS.

PulzeOS is built around this logic: not just more frames, but a smoother, cleaner and more stable gaming environment.

Because players do not only need to see high FPS.

They need the game to stay stable exactly when the moment matters.