ABOUT
The analyst, not the promises.
01What I do
I analyze and optimize Windows systems — and I measure everything. Not because measurement sounds impressive, but because the alternative is the industry default: confident claims, zero evidence.
Every optimization session I run follows a fixed protocol: baseline under controlled conditions, documented changes with sources, after-measurement under identical conditions, and a report with per-metric verdicts. When a popular tweak does nothing on your system, the report says so. That's the product.
02Why "verified"
The optimization market runs on promises — "up to 40% more FPS", "guaranteed lower latency". None of it survives contact with a controlled before/after measurement. So I built the thing the market avoids: a protocol where claims have to earn a verdict, and where "within noise" is a legitimate, reported outcome.
If that costs a sale sometimes, fine. The clients I want are the ones who prefer an honest measurement over a flattering one.
03The test bench
Development and calibration of the protocol run on my own bench: Intel Core i5-10400F + AMD Radeon RX 5700 XT. Deliberately mid-range — and stated openly, because honesty about hardware matters.
The methodology is hardware-agnostic: repeated runs, noise bands and calibrated floors work the same on any system. And every finding always declares the system it was measured on — a result from my bench is a result from my bench, never a promise about yours. That's exactly why your report starts with your own baseline.