New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it more CPU friendly when minimized to tray #1515
Comments
Thanks for opening this up. If anybody has practical suggestions on how to improve this, I am all for it. |
I've got around 15 or so projects and quite a number of tasks. I'm sort of using it to make projects and information more manageable with structure so the timing part of SP isn't essential for me right now but the highest CPU usage I've seen with SP has been around 16% but that has been temporary and only visible when I'd been jumping between projects/tasks with the app maximised or filling part of the screen and it meditatively drops to 0-3%, more often 0% when left idle/minimized, the memory it takes from the 7 tasks that it creates in KSysGuard in Linux is around 170-240 MB but not consistent. I wouldn't say that SP is overly burdensome on the system so maybe there is another issue at hand, unless of course others are also seeing the same issue. |
@NumDeP thanks for digging into this!!! I a came to the same results on my tests. There is a little bit of overhead as longer running stuff of the app is not separat from main window, I didn't finde anything too excessive. I admit that the app is maybe not lightweight, but it is not too bad neither given all the stuff it does and the cross platform support. |
This issue has not received any updates in 90 days. Please comment, if this still relevant! |
Problem Statement
After start using the program my notebook starts the CPU fans. under the CPU utilization it is visible that it takes 3-10% CPU when the app is minimized in the system tray. This is on Desktop/Linux
❔ Possible Solution
Suspend all activity when paused and leave only the timers to tick.
➕ Additional context
The text was updated successfully, but these errors were encountered: