for the CPU monitor (at least) the option “automatic range” gives a static view based on the number of CPUs instead of an adaptative range (at least for several CPUs) STEPS TO REPRODUCE 1. choose “automatic range” for a CPU monitor with many CPUs OBSERVED RESULT the graph has a fixed Y range : nbpCPU*100 instead of an adaptative range based on the real use of CPUs. EXPECTED RESULT adaptative range
To make sure I'm following, you suggest that if auto y range is on and everything is only using a max of 5% CPU, the Y should go up to 5?
It seems we do for a stacked graph.
What's the use case? Adaptive range is only a fallback when no maximum is known, like for network speed which doesn't really have a correct maximum. In all other cases, having a proper range is better. > It seems we do for a stacked graph. This was a bug that should've been fixed in the meantime, for a stacked chart we should be summing the maximums.
Created attachment 138915 [details] unstacked CPU monitor
Created attachment 138916 [details] Stacked CPU monitor (normal use)
Created attachment 138917 [details] stacked CPU monitor (intensive workload)
Dear all, thanks for your comments. Yes, it is for a stacked graph with 48 CPUs... In a normal workload, the CPU monitor is not useful at all due to the max=4800% CPU.
(In reply to Arjen Hiemstra from comment #3) > What's the use case? Adaptive range is only a fallback when no maximum is > known, like for network speed which doesn't really have a correct maximum. > In all other cases, having a proper range is better. Dear Arjen, Actually, with 48 CPU, proper range is not better. In this case, an adpatative scale is much more efficient because the amplitudes are very large and the maximum is very far from being reached in normal use (see Stacked CPU monitor (normal use)) ...Even with 5 CPUs up to 100%, it just reached 500/4800=1/10 of the height of the monitor...
Hello and thank you again for the bug report! Unfortunately we were not able to address it yet, nor even manage to reproduce the issue ourselves. Can we ask you to please check if this issue is still happening with Plasma 5.27? If it is, please change the status to REPORTED. Thanks a lot!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!