Kind of interested to know about how the graphics pipeline handles multiple processes.
Their drivers have been terrible at it for months IME; running a 3D rendering app of some sort (read: game, typically in my case, but also Google maps in a browser window for example) alongside standalone compute jobs have had much less of a disruptive effect on said 3D rendering app on Hawaii than on any other GPU I've owned in the past, NV or AMD. However, doing this has led to graphics driver hangs, or full-blown kernel panics (BSOD + system restart) within minutes, or sometimes even seconds.
Haven't dared trying under windows 10 yet, but it would be awesome if I could run Folding@Home on my GPU while playing a game like Diablo3 for example which doesn't tax the shader arrays at all really, even at 1440P rez, without having my machine keel over and die on me. World of Warcraft also runs quite well while it actually runs, that is.
Any other GPU, prior to Hawaii, has experienced incredible choppiness in any form of 3D rendering whenever the F@H client was active. Hawaii on the other hand hardly drops a single frame, even in the thickest action. Then suddenly out of the blue...your screen goes blue. Ugh.
This is particularly troublesome if you're just zooming or panning around in a map as mentioned, since it makes it difficult to use your computer for basically anything while the folding client is running if the graphics driver could go postal at any moment. Maybe they finally fixed that issue in windows 10, I don't know, but I sure as hell hope so.