[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2020-01-26 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415313 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2020-01-25 Thread Duncan
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #7 from Duncan <1i5t5.dun...@cox.net> --- So I was out a few weeks due to death in the family. =:^( Given the reverts in https://mail.kde.org/pipermail/kwin/2020-January/002999.html (including the bisected-to 00bf75d06) is this still

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-26 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #6 from Roman Gilg --- (In reply to Duncan from comment #5) > FWIW, kwin master as of 054cfc1c8 seems to be /vastly/ improved, altho not > /quite/ back to where it was. I'd say 75-80% (aka 3/4 to 4/5) of the > original regression

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-26 Thread Duncan
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #5 from Duncan <1i5t5.dun...@cox.net> --- FWIW, kwin master as of 054cfc1c8 seems to be /vastly/ improved, altho not /quite/ back to where it was. I'd say 75-80% (aka 3/4 to 4/5) of the original regression performance loss has been

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-24 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #4 from Roman Gilg --- Hey Duncan, I cleaned up the compositing path a bit more and fixed an oversight in regards to swap events not being received if the buffer age extension is not available. Please check out if this solves the problem

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-19 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415313 --- Comment #3 from Roman Gilg --- Thanks for giving detailed information. :) I was testing it with an RX 5700 XT (Navi) on Mesa master. What you could do is running Hotspot to see if there are CPU cycles being burned somewhere unnecessarily:

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-19 Thread Duncan
https://bugs.kde.org/show_bug.cgi?id=415313 Duncan <1i5t5.dun...@cox.net> changed: What|Removed |Added Status|NEEDSINFO |REOPENED Ever confirmed|0

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-18 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415313 Roman Gilg changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[kwin] [Bug 415313] Severe kwin_x11 (on amdgpu) compositing performance regression: bisected to 00bf75d06

2019-12-18 Thread Roman Gilg
https://bugs.kde.org/show_bug.cgi?id=415313 Roman Gilg changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |subd...@gmail.com CC|