V 6.6 | Slow Performance Since Upgrade?
-
Also, while I'm here, I'm hesitant to declare victory until it's been a couple of days, but so far, the slowdowns for me seem to have gone away after I updated to Vivialdi 6.7.
I've not tried any graphics driver updates because I don't have Intel graphics (I'm on a Ryzen 7), and there have been no updates to my graphics drivers in the interim. But so far, I'm hopeful.
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
@RasheedHolland Vivaldi's UX is essentially an embedded webapp, so it's quite possible for some obscure deficiency in Chromium itself w/r/t rendering to be triggered by same. It'd be one of those things where, if you can find it, would be less "fixed in Vivaldi" and more "worked around in Vivaldi until Chromium fixes it".
But doesn't the same goes for Brave and Opera? Or perhaps Vivaldi somehow interacts in a ''strange way' with Chromium which causes this problem.
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
Also, while I'm here, I'm hesitant to declare victory until it's been a couple of days, but so far, the slowdowns for me seem to have gone away after I updated to Vivialdi 6.7.
Sounds awesome. I will take 6.7 for a test drive as soon as the bug with bookmark nicknames is fixed.
I've not tried any graphics driver updates because I don't have Intel graphics (I'm on a Ryzen 7), and there have been no updates to my graphics drivers in the interim. But so far, I'm hopeful.
I have never updated my GPU drivers in 25 years of computing, I rather stay away from this type of stuff. I'm always afraid of messing things up. I did see there is a new driver for my Intel UHD GPU.
-
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
But doesn't the same goes for Brave and Opera? Or perhaps Vivaldi somehow interacts in a ''strange way' with Chromium which causes this problem.
Brave and Opera, to the best of my knowledge, both have native UIs rather than "embedded webapp" UIs. That said, I've never used Brave and haven't used Opera since the Presto days, so I don't know for certain.
I have never updated my GPU drivers in 25 years of computing,
I confess I find that nigh-impossible to believe. Perhaps you haven't explicitly manually done so, but these things get automatically updated with some regularity.
-
@Viqsi I'm pretty sure Vivaldi's webapp UI is unique in the browsing universe. It is an additional layer and thereby an expanded area where not only Vivaldi code changes, but also Chromium changes can trigger errors seen nowhere else. Further, every single machine that runs Vivaldi creates a unique environment, non-replicable by devs or testers, where some incompatibility or error may arise.
One way Vivaldi tries to defend against unanticipated friction in the interface, is to have (around seventy at present, I think) volunteer internal testers (called Sopranos), using Vivaldi on every age, capability and configuration of hardware possible, as many hours a day a possible, report back on every cock-up detected. So if any of my machines trips over anything, I report to devs ASAP. Same with the other Sopranos.
I not only use the bleeding edge of Vivaldi as my daily driver some 17 hours a day on my main Windows machine, I also test on three more towers (both Windows and Linux on one of these) and an old X86 laptop here in my office, two newer laptops that don't get turned on every day, a phone, a tablet, and two more towers (one somewhat obsolete) at my remote office when I'm there. To make matters worse, I read all the English posts in the Forum daily and try to reproduce bugs reported by users.
I'm not sure other Sopranos test on as many different kinds of hardware - in fact I'm sure they don't. No one hordes computers like me.
But when the devs and testers cannot reproduce an issue, there is no way to address it. Luckily if, say, even ten percent of users have a specific issue caused by a specific bit of code, one or more of the testers or devs is going to be able to reproduce it, and it's going to get tracked down. It's for this reason that thirty to fifty issues are resolved by the team every. single. day. And I don't even recognize most of the issues in the daily changelog, so I know even obscure glitches are being detected and remedied all the time. Yay team.
-
@Ayespy said in V 6.6 | Slow Performance Since Upgrade?:
@Viqsi I'm pretty sure Vivaldi's webapp UI is unique in the browsing universe. It is an additional layer and thereby an expanded area where not only Vivaldi code changes, but also Chromium changes can trigger errors seen nowhere else.
It's not currently commonplace but I'm not sure I'd call it unique per se. A fair argument could possibly be made that it's fundamentally a modern HTML5 twist on what Netscape/Mozilla started with XUL. (Which I remember teenage me thinking of as being OMG SO HERETICAL when it was first announced... ah, the naivete of youth).
And I'm aware of the Sopranos - many thanks to all y'all, btw. Sometimes I've considered looking for ways to volunteer, but frankly I don't have the patience for it - my bughunting sessions tend to involve lots of incoherent screaming at screens and regular trips to the fridge for more ice cream.
I would hope that Vivaldi's input would be considered very welcome by Chromium developers just by virtue of being in a position to find all sorts of (from their perspective) crazy edge cases as a result...
-
I've seen enough and it's been long enough; I'm calling it. I am no longer able to replicate this slowdowns problem with Vivaldi 6.7. (And there was much rejoycing!)
Funny thing - I also noticed this:
https://forum.vivaldi.net/topic/90135/6-2-6-6-slow-auto-complete-history-suggestions
This also seems to be a mysterious slowdown-related issue that also seemingly started with 6.2 and also seems to have been solved with 6.7. I have no idea if these are connected in any way (probably not), but the parallels amused me.I'll keep an eye out in case the slowdowns perversely deside to come back after my declaring victory, but for now, I'm happy.
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
Brave and Opera, to the best of my knowledge, both have native UIs rather than "embedded webapp" UIs. That said, I've never used Brave and haven't used Opera since the Presto days, so I don't know for certain.
Yes, you may be right. Brave and Opera don't have most of the GUI customizing that Vivaldi has, so perhaps they indeed use the native Chromium GUI.
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
I confess I find that nigh-impossible to believe. Perhaps you haven't explicitly manually done so, but these things get automatically updated with some regularity.
Yes, I've never manually updated my GPU drivers. But now that I think of it, I don't remember updating them via Win Update either.
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
I've seen enough and it's been long enough; I'm calling it. I am no longer able to replicate this slowdowns problem with Vivaldi 6.7. (And there was much rejoycing!)
Sounds cool. I remember that with Viv 6.6 I also thought it was fixed, but after 3 days or so it happened again. I assume when you say it's fixed, you mean that even after running Viv 6.7 for at least 7 days with 50+ tabs open, it won't slowdown and won't hang in memory after you close it?
-
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
Sounds cool. I remember that with Viv 6.6 I also thought it was fixed, but after 3 days or so it happened again. I assume when you say it's fixed, you mean that even after running Viv 6.7 for at least 7 days with 50+ tabs open, it won't slowdown and won't hang in memory after you close it?
Correct. Normally I would get a slowdown within 10 hours of reopening. I have gotten nothing of the sort since the update to 6.7.
-
@Viqsi yes, I think this is now fixed for me too.
I know I said this before, but has now been several days and not needed to restart due to grinding to a halt.@RasheedHolland - thanks for your posts on this, was a frustrating issue, when I've normally had a great experience with Vivaldi.
-
@Viqsi said in V 6.6 | Slow Performance Since Upgrade?:
Correct. Normally I would get a slowdown within 10 hours of reopening. I have gotten nothing of the sort since the update to 6.7.
@magilex said in V 6.6 | Slow Performance Since Upgrade?:
@Viqsi yes, I think this is now fixed for me too.
I know I said this before, but has now been several days and not needed to restart due to grinding to a halt.Sounds awesome guys. I have not tested it yet, because I'm waiting for the fix for the bookmark nicknames.
@RasheedHolland - thanks for you posts on this, was a frustrating issue, when I've normally had a great experience with Vivaldi.
Yes, I know what you mean, it was the first time I had a huge problem with Vivaldi. And the developers couldn't pinpoint the problem, but I was confident they would fix it anyway by tweaking stuff related to memory management, which they probably did.
-
@yngve said in V 6.6 | Slow Performance Since Upgrade?:
That there is a possible issue with memory management seems likely, based on what I have seen during shutdowns. But whether that is caused by something in Vivaldi's UI, or something more fundamental in the Chromium V8 engine (which handles the memory management) is something that is not possible to say at this time.
So did you guys tweak certain stuff related to memory management? Some people now believe that the problem has been fixed. Also thanks for the upcoming fix for the bookmark nicknames.
I hope you can also take a look at two other bugs. The first one is about that you guys forgot to add a mouse gesture for the ''Stack Tabs by Host'' command. And the second one is about Vivaldi not showing the ''Search Google for'' (or other search engine) command when you select text that's on top of an image. You can checkout ad.nl (Dutch newspaper) to reproduce this bug. Thanks in advance!
These are the bug reports:
VB-102809
VB-102766 -
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
These are the bug reports:
VB-102809
VB-102766Confirmed, but not dev assigned.
-
@DoctorG said in V 6.6 | Slow Performance Since Upgrade?:
@RasheedHolland said in V 6.6 | Slow Performance Since Upgrade?:
These are the bug reports:
VB-102809
VB-102766Confirmed, but not dev assigned.
Wow that was quick, thanks for checking.
I guess they were busy with other stuff, but I believe this two bugs should be easy to fix, and I've been waiting for this for at least a year, I believe.
-
@RasheedHolland I always bug tracker when asked by users to check a bug number.
-
On further review, despite declaring victory earlier, the slowdowns do seem to still be around for me - but it takes far, far more opened-and-closed tabs to trigger the issue. As in, previously I could start to see it with about 200 or so (across multiple windows); now it's closer to 2000 or possibly even higher. I hadn't previously noticed because over the last few weeks I've had to restart Vivaldi before crossing that threshold for unrelated reasons that were no fault of Vivaldi (unless you count new minor desktop updates as Vivaldi's fault ).
Unfortunately, whatever brought that order-of-magnitude improvement also rendered the "reopen workspace in new window, close the old one" workaround I'd been using nonfunctional.
I've not checked this as rigorously; I'm posting mostly because it's now happened for the third time and so I can no longer dismiss it as coincidence. So while the situation is indeed massively improved, it doesn't appear to be completely gone.