How do I enable these commands on Mac?



  • --disk-cache-dir=Z:\Vivaldi\ --disk-cache-size=1073741824

    And

    –process-per-site

    I have i5 Sandy Bridge CPU - 8GB RAM - Kingston SSD - 2GB nVidia Graphics Card and yet Vivaldi feels so sluggish as if its forced to operate I have tried various installations and reinstallations, with or without extensions, disabled in-browsers gimmicks and graphics, nothing changed it feels sticky and not fluid.

    I'm really tying to love Vivaldi and embrace it but at this point its giving me no chance to keep it even as a secondary browser, i can't deal with this ongoing lag and unusual CPU spikes when doing the simplest tasks like reading an article online.

    This will be my last attempt to see if I can fix the sluggish performance before i drop Vivaldi and come back a year or two later when its in a better place, i would've loved to keep it because I prefer to use native features that i need an extension for on other browsers

    TIA.



  • Do you really need both of those cache commands, or just the second?


  • Moderator

    @nickparkermusic said in How do I enable these commands on Mac?:

    –process-per-site

    chrome://flags/#enable-site-per-process
    Enable



  • @sgunhouse said in How do I enable these commands on Mac?:

    Do you really need both of those cache commands, or just the second?

    Does the first one make any difference?



  • The first argument probably won't work on a Mac anyway (not with drive letter Z:). And even on an SSD, I'd suppose that Vivaldi will be faster with memory cache than with disk cache, if slow behaviour / sluggishness is your problem...

    Do you have many extensions? What does Vivaldis task manager say?


  • Moderator

    @nickparkermusic The commands that you are asking about create a 1GB browser cache on a separate disk. Was there any particular reason why you needed to do this on macOS?

    I also wouldn't enable the #enable-site-per-process flag just yet. It is one of the Google-recommended Spectre mitigations but it's still an experimental feature and was not meant to be enabled in Chromium 62-based browsers. It also hasn't been tested by the Vivaldi QA team and there's a good chance that it could either break or cause some strange behaviour in Vivaldi. I wouldn't try enabling this until a Chromium 64-based Vivaldi snapshot comes out or until the Vivaldi team confirms that this is a supported configuration.

    Back to your first question, if you ever need to launch Vivaldi on macOS with any special options, the easiest way to do this is from the Terminal using the following command:

    $ open /Applications/Vivaldi.app --args WHATEVER_OPTIONS_YOU_NEED
    

    ... and replace the WHATEVER_OPTIONS_YOU_NEED part with... you guessed it.

    It's also not too hard to create a custom Vivaldi launcher on macOS (and there are a few ways to do it) but it requires some technical knowledge and a comfort level with macOS to create a simple script.



  • @morg42 said in How do I enable these commands on Mac?:

    The first argument probably won't work on a Mac anyway (not with drive letter Z:). And even on an SSD, I'd suppose that Vivaldi will be faster with memory cache than with disk cache, if slow behaviour / sluggishness is your problem...

    Do you have many extensions? What does Vivaldis task manager say?

    Not too many really. I'm confused why the same extensions use 20MB or less on Chrome while they take up to 110% more RAM on Vivaldi?

    alt text



  • @xyzzy said in How do I enable these commands on Mac?:

    @nickparkermusic The commands that you are asking about are to create a 1GB cache on a separate disk. Was there any particular reason why you needed to do this?

    I also wouldn't enable the #enable-site-per-process flag just yet. It is one of the recommended Spectre mitigations but it's an experimental feature and was not meant to be enabled in Chromium 62-based browsers. It also hasn't been tested by the Vivaldi QA team and there's a good chance that it could break Vivaldi. I wouldn't try enabling this until a Chromium 64-based Vivaldi snapshot comes out.

    Back to your first question, if you ever need to launch Vivaldi on macOS with any special options, the easiest way to do this is from the Terminal using the following command:

    $ open /Applications/Vivaldi.app --args WHATEVER_OPTIONS_YOU_NEED
    

    ... and replace the WHATEVER_OPTIONS_YOU_NEED part with... you guessed it.

    It's also not too hard to create a custom Vivaldi launcher on macOS (and there are a few ways to do it) but it requires some technical knowledge and a comfort level with macOS to create a simple script.

    Thank you so much for the detailed informative response. This will help a lot. Thank you.



  • Apparently, –process-per-site is unstable at the moment. It disabled writing text in social Flash games and although the speed improved my CPU was hitting 65% to 70%.


Log in to reply
 

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