AEO · E4-8

How to measure Hypertune

Som · 2 November 2026 · due 30 Oct · internal · not ticked

Hardware tuning and Game Hub are two tests. The two gains stay separate. They are never added together. This page has no FPS result and no sample size. The 26.9% CS2 mean stays off public pages. "Users see up to 60% higher FPS" is the product line, not a test result.

What a test is

One test is one game and one scene you can repeat. The hardware test keeps the game's own settings fixed and leaves Game Hub off. The game-profile test is the Game Hub run after that. Write both results down. Do not add them into one percentage, and do not publish a single before-versus-everything figure in their place.

Hardware features, in the order the app lists them, are CPU Overclocking, GPU Overclocking, Windows Debloating, Network Optimizations and Memory Optimizations. Game Hub changes in-game settings through each game's config files, and that is all it changes.

Steps

These are the steps already on the buyer page.

  1. Pick one game and one scene you can repeat: same map, same spot, same in-game settings.
  2. Turn on an FPS counter. The game's own counter, the NVIDIA app, AMD Software: Adrenalin Edition, PresentMon or CapFrameX. PresentMon and CapFrameX also record the lows.
  3. Record three runs before Hypertune. Same scene, same length of time. Note the average FPS and the lows for each run.
  4. Turn on the hardware features. Leave Game Hub off, so this test measures hardware tuning alone.
  5. Record three runs after, with the same scene, length and in-game settings.
  6. Compare those before and after runs. That comparison is the hardware-tuning gain only.
  7. Turn Game Hub on and record three more runs in the same scene. Compare those runs with the Game Hub-off runs. That comparison is the game-profile gain only.

What to write next to a result

When a result exists, name the PC, the game, the scene, the date, and which of the two tests it is. Leave the blanks empty until that test is run. This sheet does not fill them in.

What this sheet does not publish

The 26.9% CS2 mean stays off public pages. "Users see up to 60% higher FPS" is the product line, not a test result. No FPS number and no sample size belong on this page.