64 bit Is A Memory Hog



  • I really want to like this browser but its memory usage is absolutely ridiculous. I had 7 tabs open and no extensions installed and it was using well over a gigabyte of ram. It's memory usage should be at least 35 % lower if not more. This really needs to be addressed. Just because people have more RAM nowadays doesnt mean people dont have to optimize anymore



  • @bigboy6710:

    Sure. But also just because you have a 64bit os isn't said that you have to use the 64bit version.

    There isn't a single reason to do that, other than testing purposes. And 64 bit is marked as experimental for a reason.



  • Sure. But also just because you have a 64bit os isn't said that you have to use the 64bit version.
    There isn't a single reason to do that, other than testing purposes. And 64 bit is marked as experimental for a reason.

    im not going to argue the benefits or drawbacks of a 32bit program vs a 64bit one. But a 64bit program should not consume that much memory for the work it is doing. That was the point I was making. I was pointing out a pretty big error. no need to be a prick about it



  • Surprisingly, according to this article here, the 64bit version of Vivaldi seems to be taking up way more RAM compared to the 32bit version:

    http://www.ghacks.net/2016/01/03/32-bit-vs-64-bit-browsers-which-version-has-the-edge/

    I've been using the 64bit version for a while, and I admit that Vivaldi does use more RAM for me than other browsers like Opera, but I'm wondering whether or not I should go onto the 32bit version.

    Either way, I think this should be a mention to Vivaldi to work a bit on their 64bit version of Vivaldi to optimize it so it works a lot more like their 32bit version.


  • Moderator

    @bigboy6710:

    Sure. But also just because you have a 64bit os isn't said that you have to use the 64bit version.
    There isn't a single reason to do that, other than testing purposes. And 64 bit is marked as experimental for a reason.

    im not going to argue the benefits or drawbacks of a 32bit program vs a 64bit one. But a 64bit program should not consume that much memory for the work it is doing. That was the point I was making. I was pointing out a pretty big error. no need to be a prick about it

    It's true. There's no need to be a prick. There's also no need to use Vivaldi64 other than to test it. What you are seeing is not a "pretty big error." What you're seeing is a consequence of the fact that essentially all development efforts are being centered first on 32-bit for Windows, and the only reason a 64-bit version even exists is because it can. Refinement of it is not being actively pursued at this time, 'cuz it's low priority. Both the 32-bit and the 64-bit (even more so) are memory hogs, this is nothing new, everyone knows it including the developers, and so the announcement of this fact is sort of beating a dead horse. It's been discussed exhaustively in these forums.

    In order of priority, first the 32-bit version will be stabilized and gotten to final. Second, the 32-bit version will be optimized and refined, even while new features are being added (the 64-bit version may benefit from some spin-off of the 32-bit optimization schemes). Third, 64-bit may get some love, in an effort to make it equally stable and resource-friendly as compared to the 32-bit version.



  • @bigboy6710:

    Sure. But also just because you have a 64bit os isn't said that you have to use the 64bit version.
    There isn't a single reason to do that, other than testing purposes. And 64 bit is marked as experimental for a reason.

    im not going to argue the benefits or drawbacks of a 32bit program vs a 64bit one. But a 64bit program should not consume that much memory for the work it is doing. That was the point I was making. I was pointing out a pretty big error. no need to be a prick about it

    Yes 64bit programs (on windows) should consume more RAM but not that much.

    That said the matter isn't just on Vivaldi's guys, Most of the pro and cons at engine level comes from Google and also from the components used to build the Vivaldi UI.

    So, my personal idea is that Vivaldi is the 32bit one.

    64bit is developed to be ready when (and IF) the 64 bit browsers become really worth, and also because the less skilled users asked endlessly for it.

    As I said that's my personal idea but I believe the dev's idea isn't that far from it.


  • Vivaldi Translator

    Currently 64bit Opera 12 is using a huge amount more RAM than the 32bit version.
    I have both installed and sharing the same selection of extensions and using the same skin.

    All 64bit software can and will use more RAM for 2 reasons.

    1. 64bit calculations are bigger
    2. because it can


  • This thread made me decide to go back and try out the 32bit version. For some reason, this time I noticed it not only took less RAM(still takes a lot, but not quite as much), but I think it's snappier and more responsive than the 64bit version.

    I think it comes as no surprise why the 64bit version is experimental. I suggest sticking with the 32bit version unless you really want to try the 64bit, or you're a tester and want to test it out. Someday when they've done a lot of work on the 64bit version and made it as good as the 32bit, then that would be the best time to go for that.



  • @D0J0P:

    Surprisingly, according to this article here, the 64bit version of Vivaldi seems to be taking up way more RAM compared to the 32bit version:

    http://www.ghacks.net/2016/01/03/32-bit-vs-64-bit-browsers-which-version-has-the-edge/

    I've been using the 64bit version for a while, and I admit that Vivaldi does use more RAM for me than other browsers like Opera, but I'm wondering whether or not I should go onto the 32bit version. …

    To me, the interesting points of those test results are:-
    out of four 32 bit browsers
    a) Vivaldi ram usage with 10 tabs open is in third place (poor)
    b) Vivaldi took first place in 3 out of 5 benchmarks (middle)

    out of five 64 bit browsers
    a) Vivaldi ram usage with 10 tabs open is in second place (good)
    b) Vivaldi took first place in 2 out of 5 benchmarks (and Micosoft Edge took first in two others!! ).

    I think those are excellent results for pre release 1.0 software!
    I would think Vivaldi should maybe be more concerned about the hangs in the Dromaeo benchmark!
    Although this may be an engine problem (same for Google Chrome).

    To me the choice between 32bit and 64bit is more a user preference..


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.