https://bugs.kde.org/show_bug.cgi?id=437838
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #10 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=437838
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #8 from pierre-henri.wuille...@lip6.fr ---
(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.
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #7 from pierre-henri.wuille...@lip6.fr ---
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.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #6 from pierre-henri.wuille...@lip6.fr ---
Created attachment 138917
--> https://bugs.kde.org/attachment.cgi?id=138917=edit
stacked CPU monitor (intensive workload)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #5 from pierre-henri.wuille...@lip6.fr ---
Created attachment 138916
--> https://bugs.kde.org/attachment.cgi?id=138916=edit
Stacked CPU monitor (normal use)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #4 from pierre-henri.wuille...@lip6.fr ---
Created attachment 138915
--> https://bugs.kde.org/attachment.cgi?id=138915=edit
unstacked CPU monitor
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #3 from Arjen Hiemstra ---
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
https://bugs.kde.org/show_bug.cgi?id=437838
--- Comment #2 from David Edmundson ---
It seems we do for a stacked graph.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437838
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #1
11 matches
Mail list logo
