Hi everyone,
I’ve been testing Plasma Mobile on a couple of different hardware setups lately, but I’ve run into a consistent performance snag that I’m struggling to isolate. I’m hoping someone here might have some insight into how the KWin compositor handles resource contention.
I’ve noticed that when my system is under significant load—specifically when I’m running several background executors or testing the arceus x app environment for its multi-threading capabilities—the Plasma Mobile shell becomes quite “choppy.” The gesture navigation starts to lag, and occasionally the top panel disappears or fails to render icons properly. While I was chatting with some other users about these performance bottlenecks, it seemed like the Wayland session might be deprioritizing the shell’s rendering thread when the CPU hits a certain threshold during high-concurrency tasks.
Has anyone else noticed that the mobile UI becomes “sluggish” or starts dropping static assets if there are other high-performance tasks running in the background? I’m also seeing occasional flashes in the Maliit keyboard, which makes me think the graphics buffer is getting throttled alongside the main thread.
I’m trying to figure out if there’s a way to prioritize the KWin process or if I should be looking into adjusting the CPU governor settings to ensure the UI remains fluid in “noisy” multitasking environments. If you’ve dealt with stabilizing the Plasma Mobile experience on devices that are being pushed to their limits—or have tips on preventing these silent rendering failures—I’d really value your advice!
Best regards!