» Vivaldi Performance
-
Vivaldi is terribly lacking in performance on PCs with small amount of RAM; Why It is not like opera 12, that can be very smooth on machines with less than 512 of RAM ?
-
Efficiency and performance will still be improved, but there is only so much you can do once you for basically forced to adopt a multi-process browser engine like Blink.
-
How small are we talking? Because I haven't had an egregious experience on a tablet with 2 gigabytes of RAM. Granted, it's difficult to run anything else alongside Vivaldi but it was like that with any other browser too.
-
How small are we talking? Because I haven't had an egregious experience on a tablet with 2 gigabytes of RAM. Granted, it's difficult to run anything else alongside Vivaldi but it was like that with any other browser too.
I think the OP defined "small" with the mention of 512 GB of RAM. That's pretty small. My oldest, crummiest, 12-year-old machine running XP on a 3.5 GHz P4 has 1.5 Gb of RAM. And with that, it is incredibly slow running anything and everything, including Opera 12. Once you get past that, I have a couple of ancient towers I put Linux on, each with 2GB or RAM apiece, Two old laptops maxed out at 2GB apiece, then my "rescued" Win7 X86 with its 4GB, and this tower, with its 10 GB. Now NONE of these have any trouble with Vivaldi - at least no more trouble than with any of their programs, except I really don't dare put it on the oldest machine - the XP one. The darn thing is just too slow for anything these days.
-
Sorry, I was talking about 512 MB of Ram.
I want to congratulate Vivaldi developers team for this great renew with the super Presto engine. -
Having used a 512MB system myself until a few months ago, I can say that browsers will run fine on it as long as you don't have other heavy applications running (disable unneeded background services, real time protection software etc.) and you don't open a large amount of tabs. Indeed Opera 12 still is the best option there. Certain plugins or javascript frameworks are incredibly heavy on Opera 12 though.
I've been told that Chromium has a command line parameter allowing it to work as a mainly single-process application, and additionally that it can automatically reduce the number of instances of its rendering engine once resources run out. So it looks like Chromium-based applications have some options for improvement here.
Crash-recoverability will be important though, with excellent caching so users don't incur dataloss. Also I hope that plug-ins will still be separated when crashing and not take the whole single-process app down. -
in my case netbook and PC, tested both by windows task manager show 25% use phisical memory at the moment of start up without any browsers opened. i.e. only system uses 25% of memory in both, then when I open browser, yandex or IE or vivaldi memory grows to 45 or 50% netbook with 2 Gbits of memory at startup shows 500Mb aprox. and then 800Mb,aprox. and PC with 4 Gb of memory opens with 1GB and then up to 2 Gb at the moment of open a browser, any browser yandex, IE or vivaldi.
I test every time task manager to see if memory grows up then if I see that memory does not low at the moment of close a tab I close the browser and re open it i.e. memory is free again.
-
-
Sorry, I was talking about 512 MB of Ram.
I want to congratulate Vivaldi developers team for this great renew with the super Presto engine.It's not Presto. It's Blink. Blink is a Chromium engine.
-