Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How slow is Vivaldi:

Download fresh Vivaldi Stable - 3.6 (2165.34). Open non existent domain to land on a very light "this page doesnt exist" ERR_NAME_NOT_RESOLVED error page. Start Cloning Tabs by Shift clicking in the Tab bar, then Right clicking and selecting Clone. First you clone one tab into two, then two into four, etc. At cloning 64 Tabs to 128 opening every new Tab will be taking ~1 second per Tab. Cloning up to 256 open tabs will take you anywhere between 5-15 minutes!!! At this point switching between Tabs will FREEZE UI for 8 seconds.

Let me repeat - EIGHT second freeze while switching between empty error page Tabs.

At all times Vivaldi UI will be freezing with one maxed out thread of 16 thread 4GHz CPU, other 15 threads resting at minimal load.

Right clicking on the first open tab and selecting "close Tabs to the Right" will close 255 Tabs at once - this will FREEZE UI for ~1.5 minutes. >100 seconds of frozen UI while browser is closing 255 empty html only Tabs. Again one CPU thread maxed out, rest idle.

Welcome to a browser made using React framework.



It’s honestly terrible, I’ve mentioned this before, there’s absolutely no way I’ll ever use a browser this slow. I abandoned Firefox back in the day for much less.


I hate going "works on my machine" but I have >100 tabs open at all times and switching tabs is instant for me, and your CPU beats mine.


There is a difference between 100 and 200 tabs, plus which Vivaldi version are you on? Builds up to 3.6.2160.3 work fine with ~400 tabs, and by fine I mean ~1 second Tab switching. Instant is very subjective. You will probably also call going fullscreen on YT instant, yet here it is measured https://www.youtube.com/watch?v=-uCA2qIIG1M


I used from 2016 till 2019. While I love the features, it is too damn slow and makes browsing the Internet feel tedious.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: