https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
Keywords||usability
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
CC||arnav0...@gmail.com
--- Comment #26 from Nate
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #25 from Riccardo Robecchi ---
As I mentioned before, even just reducing the default polling to 2 seconds goes
a long way in reducing the CPU usage. While this won't fix current
installations, it will help with new ones. All other
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #24 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/libksysguard/-/merge_requests/353
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434877
alex <988a...@mail.ru> changed:
What|Removed |Added
CC||988a...@mail.ru
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #23 from Arjen Hiemstra ---
A blocking read shouldn't be using CPU unless it's actually reading something.
In this case, the CPU time spent by the read call is the time the kernel spends
building smaps_rollup. I'd love a better solution for
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #22 from Méven Car ---
(In reply to Méven Car from comment #21)
> Created attachment 168734 [details]
> flamegraph-custom-tab
I noticed the cpu time spent read proc /smaps_rollup to evaluate memory usage
is very important in particular.
It
https://bugs.kde.org/show_bug.cgi?id=434877
mirh changed:
What|Removed |Added
CC||m...@protonmail.ch
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #21 from Méven Car ---
Created attachment 168734
--> https://bugs.kde.org/attachment.cgi?id=168734=edit
flamegraph-custom-tab
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434877
Méven Car changed:
What|Removed |Added
CC||meve...@gmail.com
--- Comment #20 from Méven Car
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
CC||madc...@atlas.cz
--- Comment #19 from Nate
https://bugs.kde.org/show_bug.cgi?id=434877
Andrej Halveland changed:
What|Removed |Added
CC||andrej.h...@gmail.com
--- Comment #18 from
https://bugs.kde.org/show_bug.cgi?id=434877
Erik Quaeghebeur changed:
What|Removed |Added
CC||bugs.kde@e3q.eu
--- Comment #17 from
https://bugs.kde.org/show_bug.cgi?id=434877
Lemuel Simon changed:
What|Removed |Added
CC||lemuelsimo...@protonmail.co
|
https://bugs.kde.org/show_bug.cgi?id=434877
Till Schäfer changed:
What|Removed |Added
CC||till2.schaefer@uni-dortmund
|
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #15 from Riccardo Robecchi ---
Thank you for your detailed answer. I didn't know it was possible to manually
set the update period, so thanks for that information. I've made an experiment
which appears to confirm what I was thinking, and
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #14 from Arjen Hiemstra ---
(In reply to Riccardo Robecchi from comment #12)
> Arjen, I think I have understood why there is excessive CPU usage and I have
> a proposal on how to fix it. The problem is that System Monitor (and
> KSysGuard
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #13 from David Redondo ---
FWIW only what is seen in process and application tables is done in process.
Other data is gathered by ksystemstats and send to plasma-systemmonitor
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #12 from Riccardo Robecchi ---
Arjen, I think I have understood why there is excessive CPU usage and I have a
proposal on how to fix it. The problem is that System Monitor (and KSysGuard as
well, though to a less extent) simply poll the
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #11 from Riccardo Robecchi ---
The thing is this behaviour is not there on another desktop I own (to which I
have no access right now, due to it being in another country). There, KSysGuard
used ~3% CPU as it should.
Let's forget that for a
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #10 from Arjen Hiemstra ---
In that case it's 50% of one core, which is not different from what mine does.
It also means that this is not going to be fixed any time soon, if at all. The
problem lies with the complete lack of a kernel API[1]
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #9 from Riccardo Robecchi ---
(In reply to Arjen Hiemstra from comment #8)
> Interesting, the application table reports >50% cpu used, the application
> details says 6%. Can you confirm that the application table uses the "Line
> Chart
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #8 from Arjen Hiemstra ---
Interesting, the application table reports >50% cpu used, the application
details says 6%. Can you confirm that the application table uses the "Line
Chart (scaled to 100%)" display style?
> I see a similar issue
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #7 from Riccardo Robecchi ---
Created attachment 137076
--> https://bugs.kde.org/attachment.cgi?id=137076=edit
Screenshot with application details
(In reply to Arjen Hiemstra from comment #5)
> I run on a Ryzen 2500U as well (it has a
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #6 from Arjen Hiemstra ---
Could you post a screenshot of the Applications page with system monitor
selected and the "application details" pane visible? Especially the processes
table in the details pane would be useful.
--
You are
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #5 from Arjen Hiemstra ---
I run on a Ryzen 2500U as well (it has a Vega 8 btw, not 7 ;) ), the Vega
should be sufficiently powerful to handle everything, at least it is in my
case. However, you say you're also seeing this with KSysGuard?
https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #4 from Riccardo Robecchi ---
(In reply to Nate Graham from comment #3)
> Hmm, so probably not the same thing as Bug 429152, then.
If it's related, then I guess it's not about the GPU or the resolution as I
have a Full-HD monitor.
--
You
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=434877
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #3 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=434877
Riccardo Robecchi changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=434877
David Redondo changed:
What|Removed |Added
CC||k...@david-redondo.de
32 matches
Mail list logo
