6.2 - 6.6 | Slow auto-complete History suggestions
-
@mib2berlin
Hi, for 6 months and forum.vivaldi.net it shows 12k entries.
But I think it is not right to use the domain to count entries. The history is here to find a page you once visited and you have to remember a part of the title or URL to use it.
Yes, I am sure the database is fast enough. According to the forum, the address bar auto complete problem is about multiple searches running in parallel when typing, and a developer is working on it.But sorry, I did not really want to discuss that, as here is zero problems with the history, it was just a thought about avoiding duplicates of titles/URLs to reduce the DB size.
-
The same history I have on MacOS, so waiting for a fix.
-
@TbGbe said in 6.2 - 6.6 | Slow auto-complete History suggestions:
@BenziJunior said in 6.2 - 6.6 | Slow auto-complete History suggestions:
A new snapshot was released today,
You mean a Stable update!
Still waiting for SnapshotOh right my bad I was rather hasty and didn't read our own press release right.
I was just really keen to get feedback on the changes we are making, there are a lot of moving parts in this project.@bariton said in 6.2 - 6.6 | Slow auto-complete History suggestions:
@mib2berlin
Hi, for 6 months and forum.vivaldi.net it shows 12k entries.
But I think it is not right to use the domain to count entries. The history is here to find a page you once visited and you have to remember a part of the title or URL to use it.
Yes, I am sure the database is fast enough. According to the forum, the address bar auto complete problem is about multiple searches running in parallel when typing, and a developer is working on it.But sorry, I did not really want to discuss that, as here is zero problems with the history, it was just a thought about avoiding duplicates of titles/URLs to reduce the DB size.
We have the multiple queries queueing up already fixed and that is coming in the next release, we still have problems with individual searches being to slow, although significant progress in that area.
Sadly I was unable to get my work ready in time to make it into the our upcoming release, they should be in the first snapshot after that and barring some catastrophic regression being found when being found in testing, it should be coming in the next release after this one.
-
After finally upgrading to 6.7, I can confirm autocomplete searches are back to what they should be.
Thank you to the devs who made the fix.
And a very petty "I told you so!" to the commenters who insisted there's no way to expect a years-long browser history to perform well. (You know who you are.)
-
@BenziJunior said in 6.2 - 6.6 | Slow auto-complete History suggestions:
I'm unable to reproduce the issue with my test DB, as I'm seeing the history page load in seconds. I have some ideas as to what could be happening and will get back to you with some further questions and suggestions.
Is there any solution to fix the problem?
In version 6.7 the problem persists. -
@Isorkin
I'm sorry the idea I had didn't pan out, (and I've forgotten what it was) and I haven't had time to do a deeper dive due to more pressing issues.
I'm starting to investigate it's performance now, and talking with some collegues about improvements. -
@BenziJunior said in 6.2 - 6.6 | Slow auto-complete History suggestions:
@Isorkin
I'm sorry the idea I had didn't pan out, (and I've forgotten what it was) and I haven't had time to do a deeper dive due to more pressing issues.
I'm starting to investigate it's performance now, and talking with some collegues about improvements.My multi-year history used to bog down at times after making substantial changes - such as deleting scores of redundant entries from a particular site on a particular day - until it had a chance to "catch up" or reload following those changes. Now it exhibits similar delays whenever the browser is restarted.
I'm far from an expert in such things, but wonder if Vivaldi may be "recompiling" the full history file at start-up in ways that did not occur with prior versions. Just a thought.
-
@dem1
This agrees with my testing, so I'm investigating this exact avenue. -
@BenziJunior said in 6.2 - 6.6 | Slow auto-complete History suggestions:
This agrees with my testing, so I'm investigating this exact avenue.
Is there any progress? How can I check it?
-
@Isorkin said in 6.2 - 6.6 | Slow auto-complete History suggestions:
@BenziJunior said in 6.2 - 6.6 | Slow auto-complete History suggestions:
This agrees with my testing, so I'm investigating this exact avenue.
Is there any progress? How can I check it?
No progress except I found there are at least 3 distinct performance issues causing problems on the history page.
I was reasigned to take over other responsibilities from a collegue so this ended up on the back burner, and since the issue seems to be with the frontend I'm having someone else take over these tasks. -
@BenziJunior said in 6.2 - 6.6 | Slow auto-complete History suggestions:
No progress except I found there are at least 3 distinct performance issues causing problems on the history page.
I was reasigned to take over other responsibilities from a collegue so this ended up on the back burner, and since the issue seems to be with the frontend I'm having someone else take over these tasks.That's a shame. Probably have to go back to the old version.
It's a very uncomfortable browser experience right now.