4 ms·

If you launch Visual Studio with `devenv.exe /safemode` which "prevents all third-party VSPackages from loading when Visual Studio starts" [1] you will find Vis

If you launch Visual Studio with `devenv.exe /safemode` which "prevents all third-party VSPackages from loading when Visual Studio starts" [1] you will find Visual Studio runs extremely quickly. It's stuff like ReSharper that slows it down. [1] https://msdn.microsoft.com/en-us/library/ms241278.aspx https://msdn.microsoft.com/en-us/library/ms241278.aspx

gorohoroh 11y ago
This is not necessarily true, especially with VS2015 RTM (Update 1 is a bit better): https://twitter.com/hmemcpy/status/687257223081377792 https://twitter.com/hmemcpy/status/687257223081377792
- taspeotis 11y ago
  > This is not necessarily true Can you please clarify which part? The linked tweet talks about Roslyn. I'd expect that to be loaded because ... it's not third-party.
  - gorohoroh 11y ago
    Yes Roslyn is first party and it naturally does load, and it's very memory-intensive. You can see it happening without any extensions installed.
    - ygra 11y ago
      Memory usage and performance are two things, though. ReSharper may not add much to the memory load, but the IDE still feels sluggish.
Pxtl 11y ago
Actually, the most monstrous pig in Visual Studio for me is SSDT (Microsoft's SQL-code development environment within VS). That's a bit offtopic since it's for SQL development and not C#, and they made a little bit of improvement in 2015, but still: it's a pathetic monster. In general, anything that tries to pop-open a GUI and just drags makes me roll my eyes. EDMX files, I'm looking in your direction.
- redcalx 11y ago
  SSDT is insanely slow rebuilding our database model in the 'background'. And it's clearly tripping over itself somewhere because system CPU and IO is typically near zero while these rebuilds are running. Very annoying.
  - Pxtl 11y ago
    VS2015 improved SSDT builds, I think. Build times were cut in half, but memory usage skyrocketed. I'm supporting a legacy system that used to be north of an hour to build under SSDT. Now it seems closer to 20 minutes, if it doesn't get "Out of Memory". I do think it maxes out 1 CPU, it's just single-threaded.

gorohoroh 11y ago

This is not necessarily true, especially with VS2015 RTM (Update 1 is a bit better): https://twitter.com/hmemcpy/status/687257223081377792 https://twitter.com/hmemcpy/status/687257223081377792

taspeotis 11y ago
> This is not necessarily true Can you please clarify which part? The linked tweet talks about Roslyn. I'd expect that to be loaded because ... it's not third-party.
- gorohoroh 11y ago
  Yes Roslyn is first party and it naturally does load, and it's very memory-intensive. You can see it happening without any extensions installed.
  - ygra 11y ago
    Memory usage and performance are two things, though. ReSharper may not add much to the memory load, but the IDE still feels sluggish.

Pxtl 11y ago

Actually, the most monstrous pig in Visual Studio for me is SSDT (Microsoft's SQL-code development environment within VS). That's a bit offtopic since it's for SQL development and not C#, and they made a little bit of improvement in 2015, but still: it's a pathetic monster. In general, anything that tries to pop-open a GUI and just drags makes me roll my eyes. EDMX files, I'm looking in your direction.

redcalx 11y ago
SSDT is insanely slow rebuilding our database model in the 'background'. And it's clearly tripping over itself somewhere because system CPU and IO is typically near zero while these rebuilds are running. Very annoying.
- Pxtl 11y ago
  VS2015 improved SSDT builds, I think. Build times were cut in half, but memory usage skyrocketed. I'm supporting a legacy system that used to be north of an hour to build under SSDT. Now it seems closer to 20 minutes, if it doesn't get "Out of Memory". I do think it maxes out 1 CPU, it's just single-threaded.