In general, at work and at home there is Visual Studio 2017 with the same plug-ins, for example ReSharper, but at work it starts quickly than at home, although at home the computer is more powerful:

The home is the Core I7 3770K vs working Core I5 ​​1 or 2 generations.

Windows 10 vs Home on Windows 7

Home frequency 8 GB 2333 vs working 8 GB 1333

The drives at home and at work are standard HDDs with the only difference being that I have 1 TB at home, and at work 500 GB.

It seems that if at home VS should start no faster, then at least not worse.

In fact, when you start the HDD schedule goes to the ceiling and VS runs for 10 minutes.

Where to dig?

  • Dig towards SSD. Well, or try to run on a clean system. Although ssd is better. - don Rumata

1 answer 1

10 minutes to start is some kind of madness. My VS 2008 runs 3 seconds, and VS 2017 starts in 6-7 seconds, from the moment of a double-click on the icon to the full opening of all tabs with the source code of a large project. An ancient 6-core Fen with 16GB of memory, but a disk with 512GB SSD on which everything is - system, studio, all projects.

So put the SSD and forget it all like a bad dream.

  • Well, at work on the HDD, it starts more quickly. - iluxa1810
  • Maybe the problem is in the home HDD? - Bakhuss
  • @ iluxa1810, there may be a million reasons. For example, a disk is 7200 at work, and you have 5400. In general, disks are different, and this number has a noticeable effect on such a number of operations. - freim
  • LOL, it turns out I have my HDD, which supported SATA3 were connected to the SATA2 interface. - iluxa1810
  • @ iluxa1810, it hardly affected somehow, even for SSD, the difference between the SATA2 and SATA3 interfaces is noticeable only on synthetic tests. Most likely you just drive slower. You see what model HDD, then you can objectively compare. - freim 1:21 pm