Skip to content
MonkeyOverlaysMonkeyOverlays

Performance

Integrated capture measures your session on an opt-in basis. No overall Windows benchmark results have been published yet.

  1. In the main window → Performance, click Start capture.
  2. Drive or play a session for a few minutes.
  3. Click Stop and save.

The JSON is saved in Documents\MonkeyOverlays\Rendimiento\captura-<date>.json. It is not sent automatically: sharing is a manual action.

One sample per second: app and WebView2 window CPU/memory; core processor time per topic; FPS and CPU/GPU usage reported by iRacing. Process CPU is expressed as a percentage of the whole machine.

Includes version, operating system, CPU, cores, RAM, visible widgets, stream composition, displays and OBS state. Does not include driver names, IDs or account data. Review machine context before sharing.

Declared widget rates limit updates; they do not guarantee FPS. The CPU target still needs real-machine measurement. To evaluate impact, repeat the same replay with identical graphics, resolution and duration, first without overlays and then with your composition. Compare multiple runs, not an isolated sample.

OBS statistics describe all of OBS and cannot attribute its entire cost to MonkeyOverlays. We do not publish performance figures before measuring them.