[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-20 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 marcin.ba...@gmail.com changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #10 from marcin.ba...@gmail.com --- I attached profiling results on Nvidia and Intel. Steps: 1. Start copy files in dolphin 2. Run command: timeout [t]s ./apitrace trace --api gl plasmashell where t = 30s, 50s Because of attachments limit

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #9 from marcin.ba...@gmail.com --- Created attachment 104085 --> https://bugs.kde.org/attachment.cgi?id=104085=edit 30s Intel apitrace Command: timeout 30s ./apitrace trace --api gl plasmashell -- You are receiving this mail because:

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #7 from marcin.ba...@gmail.com --- Created attachment 104083 --> https://bugs.kde.org/attachment.cgi?id=104083=edit 30s Nvidia apitrace Command: timeout 30s ./apitrace trace --api gl plasmashell -- You are receiving this mail because:

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #8 from marcin.ba...@gmail.com --- Created attachment 104084 --> https://bugs.kde.org/attachment.cgi?id=104084=edit 50s Intel apitrace Command: timeout 50s ./apitrace trace --api gl plasmashell -- You are receiving this mail because:

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #6 from marcin.ba...@gmail.com --- Created attachment 104082 --> https://bugs.kde.org/attachment.cgi?id=104082=edit 50s Nvidia apitrace Command: timeout 50s ./apitrace trace --api gl plasmashell -- You are receiving this mail because:

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #5 from David Edmundson --- >The difference is QSGRenerThread uses more CPU time when Nvidia is used. Well that's a given. On intel there is no render thread. you can force nvidia in there too if you run

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #4 from marcin.ba...@gmail.com --- The difference is QSGRenerThread uses more CPU time when Nvidia is used. > Exactly what perf command did you run? perf record plasmashell with native nvidia drivers and intel. For clarity: I have 2

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-17 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #3 from David Edmundson --- That shows us nothing. There's 1.8% of CPU time spent in renderMergeBatches in the nvidia one and 1.4% in intel. A .4% difference in CPU time isn't going to be significant difference

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #2 from marcin.ba...@gmail.com --- Created attachment 104063 --> https://bugs.kde.org/attachment.cgi?id=104063=edit Perf Intel Attached report from perf profiling tool plasmashell+intel driver -- You are receiving this mail because: You

[plasmashell] [Bug 376485] High CPU usage with Nvida native driver

2017-02-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=376485 --- Comment #1 from marcin.ba...@gmail.com --- Created attachment 104062 --> https://bugs.kde.org/attachment.cgi?id=104062=edit Perf Nvidia Attached report from perf profiling tool plasmashell+nvidia native driver -- You are receiving this mail