#5420 (Enhancement) relatively high CPU usage of profile loader applet on Windows

+1 0

Closed as Won't Fix
Component: DisplayCAL 3.2.3
Created by

Last modified


I've noticed when my computer is idle and I have no applications running, that the dispcal profile loader tray applet is using a relatively high amount of CPU.

Using Task Manager and sorting by CPU usage, the applet is usually in the top three. It uses between 0.1% -> 0.3% (I saw 0.5% once) of the CPU resources. In comparison all the windows OS services and background apps are 0%. I would expect the tray to be similar at 0% given that its job is to only check occasionally and only then to take action to correct profiles.

The full command line of this process is:

"C:\Users\Dale\AppData\Local\0install.net\implementations\sha256new_P4A5C2LXKZJ4APVA2ABBTNLTNR3UWKVELBEPG5BAZXUMLMP6B66Q\pythonw.exe" C:\Users\Dale\AppData\Local\0install.net\implementations\sha1new=a01b4850a9e1763ecdc59d1888ed664384683db0\DisplayCAL-apply-profiles.pyw --task pythonw.exe

Setup:
Windows 10 x64 with current updates
Clevo p150em based laptop with 16gb ram and Intel i7-3720qm @ 2.6Ghz

Logs attached

 


DisplayCAL-logs (application/x-gzip | 2017-01-08 03:11:48)


3 thoughts on “relatively high CPU usage of profile loader applet on Windows”

  1. dispcal profile loader tray applet is using a relatively high amount of CPU. […] It uses between 0.1% -> 0.3% (I saw 0.5% once)

    I am not sure how you got the idea that <=0.5% CPU usage constitutes a “relatively high amount of CPU”. The Windows Desktop Window Manager (dwm.exe) already uses more on average (around 0.3% constant) on my i7 system.

    I would expect the tray to be similar at 0% given that its job is to only check occasionally and only then to take action to correct profiles.

    It is effectively 0% idle and every three seconds it checks running processes (to be able to turn itself off temporarily if needed), checks for profile changes and reloads the calibration (on Intel graphics hardware this is done twice to circumvent a driver bug, but apparently this doesn’t really add tangible overhead compared to the CPU usage numbers I get on my system with nVidia). There is no headroom for optimization here. Closing as wontfix.

  2. OK. I don’t want any misundersanding. In my experience, DisplayCAL is good software. I saw the unusual CPU usage and wanted to report it to you with helpful intentions.

    Relatively…as in relative to all the other processes currently running. It was in the top 3 and comparable in CPU usage to two other processes doing (what seems) much more active things. Yet I knew dispcal applet was doing only the things you describe above.

    Perhaps it is pythonw.exe itself. You app is a python applet so while you app’s code may not be using much CPU…perhaps pythonw itself it using a measurable amount of CPU to manage memory, wait timers, callbacks, clocks, etc.

    Thanks for considering the feedback. Happy new year!

  3. OK. I don’t want any misundersanding. In my experience, DisplayCAL is good software. I saw the unusual CPU usage and wanted to report it to you with helpful intentions.

    No worries.

    perhaps pythonw itself it using a measurable amount of CPU to manage memory, wait timers, callbacks, clocks, etc.

    No, not really. Even with the GUI thread running, a Python app that does nothing but wait for user input has effectively 0% CPU usage in task manager.

Comments are closed.