Close unused tabs-The more tabs that users have open simultaneously, the harder Chrome Browser has to work.

For details, see Use Chrome Browser with roaming user profiles.

Roaming user profiles-Turn on roaming user profiles so that users have a consistent Chrome Browser experience each time they use the browser on a virtual desktop.For information, see Set Chrome app and extension policies (Windows). Google recommends that you limit the number of extensions that users can install.

Extensions-Extensions can use a large amount of memory or increase the amount of time it takes to start Chrome Browser.Hardware acceleration-If your VDI server doesn’t support graphics processing units (GPUs), use Group Policy Management Editor to set the Use hardware acceleration when available policy to false.For example, to let 100 users simultaneously use Chrome Browser on virtual desktops, you need at least 100 GB RAM and 200 vCPUs. Check to make sure that these recommendations suit your organization. For Chrome Browser, Google recommends 1 GB RAM and between 2 and 4 virtual central processing units (vCPUs) per virtual desktop. Server memory and CPU size-The number of users who can simultaneously use Chrome Browser on virtual desktops depends on your VDI servers’ memory and CPU resources.If Chrome Browser is running too slow or using too much memory, here are some suggestions for how to improve Chrome Browser performance in a VDI environment. For administrators who manage Chrome browser on Windows for a business or school.Īs an administrator, you can deploy Chrome Browser in a virtual desktop infrastructure (VDI) environment such as Citrix ® Virtual Apps and Desktops.

System optimizer windows 10 browser