3 ms·
For reference to what slow user interface means I did some comparisons to Chrome and best case scenario (cloning super light 404 pages) Opening tabs is ~5-20x s
by rasz 6y ago
For reference to what slow user interface means I did some comparisons to Chrome and best case scenario (cloning super light 404 pages) Opening tabs is ~5-20x slower, while closing tabs is over 1000x slower. Closing tabs is so slow you can actually see them closing one at a time (after selecting close all tabs). Vivaldi UI is written in javascript (react) and runs as blocking single thread - Firing slow operation like closing a tab means UI freezes and stops accepting new commands for up to one second. Going fullscreen on Youtube can also take over one second.
https://www.youtube.com/watch?v=-uCA2qIIG1M https://www.youtube.com/watch?v=-uCA2qIIG1M
>going full-screen on YT: over 1 second
>returning from full-screen on YT: over 1.2 seconds
>opening Tab: 700 millisecond, 1.75 seconds, 3.453 seconds, 6.078 seconds, 7.734 seconds
>opening Tab totals: 0.700-7.7 seconds
>closing Tab: 1.468 seconds, 2.407 seconds, infinity because browser lost the Click event, 968 millisecond, 1.390 seconds, infinity, 700 millisecond
>closing Tab totals: 0.7-2.4 seconds or infinity if you aren't lucky
>time you have to wait after opening few tabs in background for the page to regaining usability: 11 seconds!
All of that on 4GHz Haswell.
Vivaldi is Gmail levels slow, new Youtube levels slow. Remember kids, dont do UI in javascript.