Def woudl like to take this. My understanding is that .Net themselves recommend being wary about server-gc as it can so effectively saturate the machine with work. We def want the benefits of the improvements there, but not at the expense of the host VS process. So this is a very easy way to get a best of both worlds outcome here.

Can this cause issues where, when a GC isn't happening, we might have VS starving off the "background" work the user actually wanted?

(not opposing, but just wondering if this can have "interesting" side effects to be on the lookout for)

Can this cause issues where, when a GC isn't happening, we might have VS starving off the "background" work the user actually wanted?

I haven't seen this happen. What I've seen happen several times is OOP using CPU and causing severe delays in devenv.exe and/or VBCSCompiler.exe.