2 ms·
Chrome on my MBPr is also dying in a fire here. Chrome on OSX is known for extremely shitty performance because it usually (always?) switches acceleration off.
by DiabloD3 11y ago
Chrome on my MBPr is also dying in a fire here. Chrome on OSX is known for extremely shitty performance because it usually (always?) switches acceleration off.
If chrome://gpu/ says hardware rasterization is disabled, set chrome://flags/#enable-gpu-rasterization to enabled.
Chrome on Windows also will disable acceleration by default if it detects both an Intel and either AMD or Nvidia chipset enabled at the same time, thinking its a hybrid solution (even when it's obviously not, such as an extremely common desktop i5/i7 + high end GPU setup).