![]() On the other hand if you want maximum performance all the time, then discrete only will make sure the most powerful GPU is fired up.įor most situations OS X does a decent job of managing power considerations, but if you want a little more control, gfxCardStatus will let you set up GPU power schemes to define which chip is used depending on power source. If you want to save as much battery power as possible, leaving it on integrated only will ensure that the power hungry discrete GPU doesn't fire up. A drop down menu provides you with three options: Integrated Only Discrete Only and Dynamic Switching, which is the system default that lets OS X decide which graphics card is required. Sitting up in your menu bar, gfxCardStatus shows you at a glance which card is currently active, but more than that, it actually allows you to manually switch between the GPUs. That's where gfxCardStatus comes to the rescue. It's often tricky to know which card is currently in use as the switch between the two is seamless. about:memory is the best way to tell if WebGL is actually being used.Some newer MacBook Pros have been packing dual graphics cards for a while now, with the ability to dynamically switch between them - integrated for battery life and discrete for performance. Manually switch to Integrated Only or Discrete Only mode to force one GPU on or the other. The Dependencies list: open the gfxCardStatus menu when your discrete GPU is active to see what is turning it on. features: Growl or Notification Center notifications when the GPU changes. Regarding Google Maps: note that it only uses WebGL if you enabled 'MapsGL'. d youre using the higher-powered discrete GPU. As the last WebGL context goes away, gfxCardStatus should switch back to 'i'. Wait until GC happens so the WebGL contexts actually go away: you can go to about:memory to check if it still mentions WebGL under 'other measurements', and use the GC/CC buttons to accelerate them going away. Close all tabs that uses WebGL but keep Firefox open. Visit a page that uses WebGL, for instance. If the currently used GPU is the discrete one (icon is then 'd'), try quitting applications until it's switched back to 'i'. Make sure you're in the default auto-switch mode, and that the currently in-use GPU is the integrated one (gfxCardStatus's icon should be 'i'). On older macs, you can only force one GPU or the other. You can verify that by looking at the gfxCardStatus menu: only on supporting Macs does it offer the default/auto-switch option. install gfxCardStatus (Marcia's link) and verify that your mac supports dynamic GPU switching (only recent Macs do). That would be done by delaying the destruction of the dummy context when its refcount hits 0. Then for the actual WebGL context's OpenGL context, do not change anything (keep sharing, keep AllowOfflineRenderers).Īpple asked us to debounce GPU switching. That should be a global refcounted object. So the idea is: during WebGL context creation, just before creating the actual WebGL context's OpenGL context, create a dummy context without AllowOfflineRenderers. The usefulness of such a dummy context comes from the fact that it doesn't have to share resources with any other context, so we are free to choose its attributes. So if we create a dummy OpenGL context without AllowOfflineRenderers, we will switch immediately to the discrete GPU and stay there as long as this context is alive. The idea is that, except possibly in corner cases that we could detect if needed, only one GPU is used at a time. Not sure if it's been written down before, so here it is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |