Repository navigation
[Bug] Background CPU usage abnormal / spikes #37
Description
Activity
@sjclayton thank you for raising this. The 5-8% typical on Linux definitely seems high from what we've observed. Do you mind sharing your system specs so we can test on a similar machine?
We'd love to have CPU similar to
mtrbut it's worth noting Orb differences that make it an ambitious goal:- There are two ongoing pingers (first hop and internet) collecting metrics every 500 ms
- Pingers use different protocols (TCP, QUIC, ICMP)
- Lag is a bit more complex and aims to mimic real-world protocol behavior
- Local storage and aggregation (Orb Score) via SQLite
- Orb Cloud for notifications, remote status, etc.
That said, our goal is definitely to make Orb more and more efficient. We have some ideas for optimizations that we'll work on for the next release.
Reacted by Shaun ClaytonI'd like to add that I am also experiencing an average usage of around 6% with occasional spikes when Orb is backgrounded on Windows 11. The primary culprit seems to be a subprocess labelled
WebView2 GPU Processat around 4-5%, followed byWebview2: wails.localhostat around 1%.CPU is an 8700k just so the percentages aren't completely arbitrary. It's using more than my browser with multiple tabs open by a fairly large margin which is definitely unexpected for a monitoring app.
For me on my Raspberry Pi 4B 8GB, Orb averages 20-30% CPU usage...
Describe the bug
I've experienced background CPU usage being higher than it should be for a service like Orb, typical background CPU usage typically in the 5-8% range, with spikes in the 15-25%+ area every 5-10 seconds (even when a speed test is not currently running). This is not what I would consider normal for something that is primarily a monitoring daemon (service). I have observed this primarily on Linux, but also on Windows 10 clients (even when the app is not open in the foreground).
For comparison purposes, running
mtr(which runs a constant traceroute / ping) and is not even running as a service, uses in the range of 0.5-2% CPU while actively running.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Background CPU usage more consistent with similar services.
Environment (please complete the following information):