Speeddial poor performance with release: 3.0.1 and QtWebEngine-Release 5.12.0 STEPS TO REPRODUCE 1. Start Falkon 2. Open new tab (configured that a new tab always shows speeddial) or 3. Move around with the mouse pointer over an opened speeddial. OBSERVED RESULT Almost 4 complete threads of 8 (I7, hyperthreading activated, Intel graphics) are busy - for some seconds when a new tab is opened / as long as the mouse pointer is moved. EXPECTED RESULT Just a moderate increase of processor activity. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: 4.19.9-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.14.4-1 KDE Frameworks Version: 5.14.4-1 Qt Version: 5.12.0 ADDITIONAL INFORMATION
Hello, I can add that it takes very long time to load with my external monitor (5:4 > 1280:1024px) and performance is on ice.
Removing custom background image and using the stock one helped me to increase performance when speeddial was already loaded, otherwise it was unusable.
I have an i7-6700 and while all threads do jump a little when opening the Speed Dial tab and moving the mouse none hit 100% and there is no freezing. Stephan/Juraj can you please re-check on Falkon 3.1.0 and confirm if the issue is still present.
(In reply to Justin from comment #3) > I have an i7-6700 and while all threads do jump a little when opening the > Speed Dial tab and moving the mouse none hit 100% and there is no freezing. > > Stephan/Juraj can you please re-check on Falkon 3.1.0 and confirm if the > issue is still present. If you have powerfull CPOU you do not see/feel it, you CPU will do the job. But if you have slower CPU you can see/feel it because CPU has not enough power. This is valid bug, speeddial needs a rewrite because it is too slow. The loading time is long and the response from it is also slow. You say it does not hit 100% on your CPU, good joke. On my laptop with Pentium B980 (2 core only) it hits 100%. On my PC Ryzen 5 3600 (6 cores, 12 threads) there are 4 "core"(probably threads) out of 12 which hist around 10% to 20% usage on speeddial while on other pages everything is around 0%. It may also depend on the CPU used. On modern CPU it is not so dramatic but on lowerend modern CPU I bet you will still feel/see it. While I agree that 10%-20% on 4 threads on new modern CPU is not 100% it can vary depoending on your CPU (age, type, cooling, laptop) and also qtwebengine version. For my quick test I used QtWebEngine 5.15 and latest Falkon code.
(In reply to Juraj from comment #4) > (In reply to Justin from comment #3) > > I have an i7-6700 and while all threads do jump a little when opening the > > Speed Dial tab and moving the mouse none hit 100% and there is no freezing. > > > > Stephan/Juraj can you please re-check on Falkon 3.1.0 and confirm if the > > issue is still present. > > If you have powerfull CPOU you do not see/feel it, you CPU will do the job. > But if you have slower CPU you can see/feel it because CPU has not enough > power. > > This is valid bug, speeddial needs a rewrite because it is too slow. > The loading time is long and the response from it is also slow. > > You say it does not hit 100% on your CPU, good joke. > On my laptop with Pentium B980 (2 core only) it hits 100%. > On my PC Ryzen 5 3600 (6 cores, 12 threads) there are 4 "core"(probably > threads) out of 12 which hist around 10% to 20% usage on speeddial while on > other pages everything is around 0%. > > It may also depend on the CPU used. > On modern CPU it is not so dramatic but on lowerend modern CPU I bet you > will still feel/see it. > > While I agree that 10%-20% on 4 threads on new modern CPU is not 100% it can > vary depoending on your CPU (age, type, cooling, laptop) and also > qtwebengine version. > > For my quick test I used QtWebEngine 5.15 and latest Falkon code. I don't disagree at all that it needs to be performant on as many systems as possible. However the original reporter advised they had an i7 CPU as well, so I was comparing Apples with Apples. I did see that it loads each item on the Speed Dial to render the page which seems quite inefficient. I would suggest a logo or something instead of each speed dial, that way it's not fetching each page and rendering it all at once.
(In reply to Justin from comment #5) > I don't disagree at all that it needs to be performant on as many systems as > possible. However the original reporter advised they had an i7 CPU as well, > so I was comparing Apples with Apples. > > I did see that it loads each item on the Speed Dial to render the page which > seems quite inefficient. I would suggest a logo or something instead of each > speed dial, that way it's not fetching each page and rendering it all at > once. User never stated exact CPU, it could be the oldest of them all. If you are so persistent on closing this bug, can you create another one with more "proper" description and tests (if there is not alreade)? Thank you.
(In reply to Juraj from comment #6) > (In reply to Justin from comment #5) > > I don't disagree at all that it needs to be performant on as many systems as > > possible. However the original reporter advised they had an i7 CPU as well, > > so I was comparing Apples with Apples. > > > > I did see that it loads each item on the Speed Dial to render the page which > > seems quite inefficient. I would suggest a logo or something instead of each > > speed dial, that way it's not fetching each page and rendering it all at > > once. > > User never stated exact CPU, it could be the oldest of them all. > If you are so persistent on closing this bug, can you create another one > with > more "proper" description and tests (if there is not alreade)? > Thank you. I'm sorry if I have upset you, I'm not aiming to close bugs if they are still valid. I'm trying to confirm if they are still valid and if so bring them to the developers attention.
(In reply to Justin from comment #7) > I'm sorry if I have upset you, I'm not aiming to close bugs if they are > still valid. I'm trying to confirm if they are still valid and if so bring > them to the developers attention. There is not a problem with that. As I mentioned I myself experienced this behaviour on my laptop for many years. So even if the reporter could encounter some edge case with i7 of unknown age I still consider it as valid because the performance is too poor. My other thought was: CPU usage should stay low, the 20% I managed to get is still too much.
As I was annoyed by the described effect meanwhile I have created an own html-starting-page with a collection of the links I use most. As this is really loaded 'in a snap' I have a workaround which is more than just 'satisfying' for me. But I have tried out the speeddial of the new version and find it noticeably more responsive than before. Nevertheless I'll keep my own solution ;) . Regards Stephan
Hey KDE Team, I am new here so pleas let me know if this is not the correct way of going about this. I wanted to create an issue for Falkon (and got hear through gitlab). But since this looks different to GitHub/Lab I am not 100% sure about the does and dont's --- **My related issue** I have started using Falkon, on Fedora 38 as well as Windows 11 and on both I can not set a custom background in the speed dial without breaking Falkon. Both give me a window with App does not respond: Wait or Force Quite. Waiting does not help.