Comments

8 comments

  • Forrest Smith

    sorry, I think the default behavior is the only supported option.

     

    You could specify a chromium cmd line option "--process-per-site" somehow in order to try to force that variant of the behavior, but I'm not sure, off hand, where you'd place that option for the OS, or even if it would work at run time (as opposed to being built in).

     

    If your machines have 1 GB of RAM and you're not multi-tasking too much, I would guess you won't have memory management issues. With 2 GB you should have plenty. 

    0
    Comment actions Permalink
  • SysAdmin GFS

    Thanks, but that's not our experience.  Most of our Chromebooks and other ChromeOS devices have at least 4GB and this is not always sufficient depending on the webpages accessed.  This particular user is a power user and could make use of the better process model, which we do use on other platforms running Chrome.

    0
    Comment actions Permalink
  • Forrest Smith

    As far as I know, adjusting this is not possible on an official Chromebook, and when in doubt we typically aim to parallel that experience as closely as possible. What approach do you use on official Chrome devices?

    0
    Comment actions Permalink
  • Kathy Bible

    My computer was wiped and the Cloudready OS was installed. Because my computer was wiped...what operating system if any would my computer have if for some reason I had to reset it or preform a powerwash??? Thanks.

    0
    Comment actions Permalink
  • Forrest Smith

    Kathy,

    When CloudReady is installed it overwrites everything on the device.

    If you have a Windows, MacOS, or Linux installer that you made or from a 3rd party, you can use that to overwrite CloudReady and install a different OS. Without something like that, any resetting or powerwashing you did would be internal to rhe CloudReady OS and would simply be removing user-data to leave you with a like-new image of CloudReady.

    0
    Comment actions Permalink
  • Kathy Bible

    Thanks,  that was just what I needed to know.  I needed to understand that powerwashing would only remove user-data and not in any way harm my Cloud Ready OS.  Thanks.

    0
    Comment actions Permalink
  • Peter Smulders

    Maybe the chrome flag #enable-site-per-process can be used?

     
    0
    Comment actions Permalink
  • Forrest Smith

    Peter - 

     

    Good call - that is the right solution and is available in v61.

     

    When we publish v63 in the next month (or less) that option will also be something that administrators of Education or Enterprise CloudReady can enable for groups of users via the Google Admin Console.

    0
    Comment actions Permalink

Please sign in to leave a comment.