Light on your streaming PC
We measured Jlerts' CPU and memory use in three setups, from a single overlay to a busy multi-scene stream with three chats. These are real measurements of the app, with alerts firing and chat scrolling.
CPU and memory, by setup
Each bar is split into the Jlerts app itself and the overlays and chats OBS shows (the browser sources). Switch between the app minimised to the tray (how it runs while you stream) and with its window open (while you edit). Hover a bar for peaks.
The three setups
Tier 1: Basic
One overlay with alerts, plus two goals on screen.
Tier 2: Standard
Two overlays (normal and vertical, for dual-format streams), one chat box and four goals.
Tier 3: Heavy
Three overlays and three chats (a chat in a TV frame, a ticker and full-screen snowfall chat) plus six goals, as if several scenes each use different overlays.
How we measured
- The real app (the same build you download), minimised to the tray or with its window open, with its own test data.
- Each overlay and chat was opened at its OBS size in a hidden Chromium browser, the same engine OBS's browser sources use.
- During each run, an alert played every 6 seconds and chat got 2 messages a second (a busy chat), with emotes and profile pictures.
- After a 20-second warm-up, CPU and memory were sampled every 2 seconds for a minute.
- CPU is the share of the whole processor (all cores), like Task Manager's Processes tab. Memory is RAM in use (Task Manager's "Memory" column).
- OBS's own encoding and capture aren't included: those are the same whatever alert tool you use.