• 0

VS2010 Load Time


Question

Hi there,

I was wondering what people's load times of VS 2010 is. I'm trying to establish if my PC needs upgrading and that VS 2010 could be faster if that was the case.

My PC is Aspire 7540g, AMD Athlon II X2 M300, Mobility Radeon HD4570, 4GB, 7200 RPM drive, W7-64Bit, VS2010SP1.

My WEI is processor 4.9, Memory 7.0, Graphics 4.9, Gaming Graphics 6.3, Hard Disk 5.9

Initial load of VS 2010 is 25-30 seconds, subsequent loading times around 20 seconds.

Thanks,

Simon.

Link to comment
https://www.neowin.net/forum/topic/1004220-vs2010-load-time/
Share on other sites

19 answers to this question

Recommended Posts

  • 0

A lot of it can depend on your addons too. An out-of-the-box install can load rather quickly, a few seconds on my machine if I recall. Once I load it up with various addons, it can take a fair bit longer. CodeRush/ReSharper/etc tend to be the biggest offenders there.. absurdly handy but also takes a fair bit extra in time and resources to run. As much as I love the 2010 IDE, it can be fairly piggish.. pretty quick once it's up and running (if you got the memory for it), not so much when it first starts up.

Depending on your needs of course you don't have to use the IDE. Occasionally I'll just work with another editor for quick changes, large builds I tend to do from a console versus the IDE, etc etc. Shoot I've even used VIM on occasion for giggles when I'm in a retro mood.

  • 0
VS 2010 is slow. I have already seen so many guys who have switched back to VS 2008 because of sluggishness of VS 2010. Even on my Core i7 it takes more than 5 seconds to load. SP1 didn't fix the problem either (Nothing new, the same thing happened with Vista too)

Just my own observations, but VS2010 is slow to load on a cold start, subsequent loads typically take a couple seconds tops. Once it's up and running I personally found it to be significantly quicker than 2008, never mind missing the platform and IDE features that aren't available in 2008.

  • 0

turn the splash off, MS put a programmed delay in it on the first load to make it show, after that it doesn't not sure how they pulled that off but they somehow did... add the argument /nosplash to devenv.exe for the VS link you will cut a few seconds off the initial load time

  • 0

VS 2010 is slow. I have already seen so many guys who have switched back to VS 2008 because of sluggishness of VS 2010. Even on my Core i7 it takes more than 5 seconds to load. SP1 didn't fix the problem either (Nothing new, the same thing happened with Vista too)

oh please, every freaking VS release I hear this same comment...... VS 2002 is slow I went back to VS6..... VS 2005 is slow I went back to 2002, VS 2008 is slow I went back to VS2005...... now once a freaking gain..... VS2010 is slow,THEY ARE ALL SLOW! The IDE environment is MASSIVE no mater what with the flexability of the IDE it will be slow somewhere at somepoint, its a generic shell written to support ANY programming language if someone makes a add-in and templates for it...

If you want to see slow, our main solution has 120 projects in it (about 3 million lines of code).... it takes 5 MINUTES! to load but after that it's fine... biggest slow down is the setup projects, which for some reason are slow loading by nature... and source control get auto status update adds to it also

  • Like 1
  • 0

A lot of it can depend on your addons too. An out-of-the-box install can load rather quickly, a few seconds on my machine if I recall. Once I load it up with various addons, it can take a fair bit longer. CodeRush/ReSharper/etc tend to be the biggest offenders there.. absurdly handy but also takes a fair bit extra in time and resources to run. As much as I love the 2010 IDE, it can be fairly piggish.. pretty quick once it's up and running (if you got the memory for it), not so much when it first starts up.

Depending on your needs of course you don't have to use the IDE. Occasionally I'll just work with another editor for quick changes, large builds I tend to do from a console versus the IDE, etc etc. Shoot I've even used VIM on occasion for giggles when I'm in a retro mood.

have you ever opened a web.config file directly in VS2010 or VS2008 just to do a quick edit? external to the solution you are in, just like right click web.config open in VS?... we always have this odd delay, it takes about 1 minute to open the file like it has to think about what to do, after that opens fine and saves fine.... every one of our dev machines repos this... always been an odd behavior, and MS always closes our bugs on it as "by design"

  • 0
have you ever opened a web.config file directly in VS2010 or VS2008 just to do a quick edit? external to the solution you are in, just like right click web.config open in VS?... we always have this odd delay, it takes about 1 minute to open the file like it has to think about what to do, after that opens fine and saves fine.... every one of our dev machines repos this... always been an odd behavior, and MS always closes our bugs on it as "by design"

Mmm I don't use much ASP.NET (more often than not I typically go the PHP route for web based stuff via VS.PHP, most of the servers I work with are running BSD and I'm not thrilled with Mono in its current state), most of the time I have VS loaded it's for PHP, a desktop application or a system service, some managed, some not. As a guess it's probably reparsing and validating dependencies, etc etc once it sees the file was changed, but I'm the wrong person to ask for troubleshooting ASP.NET.. I don't recall a delay though.

Make sure you've updated to service pack 1. VS2010 loads almost instantly for me whether it's the first start of the day or 10th.

In my case it's probably my addons.. I have a bunch, and I know CodeRush/Refactor Pro is one of my biggest offenders. I can live with the delay though.. I love those addons to death. If I have it disabled though yea mine's near instant to start. That's on a current OS mind you; on a test VM running ye olde XP it's significantly longer thanks to a lack of SuperFetch.

  • 0

System: Dell Studio 17 laptop (purchased January 2009)

CPU: Intel Core 2 Duo at 2.53Ghz (T9400)

RAM: 2x2GB Samsung DDR2 PC2-6400

HDD: 2x Western Digital 320GB 7200RPM SATA2 (model: WD3200BJKT) - no RAID configuration just two independent drives running in AHCI mode. All applications are installed on the same drive as the operating system and pagefile.

Graphics: 256MB ATI Mobility Radeon HD 3650 (dedicated)

OS: Windows 7 Ultimate x64 SP1

WEI: 5.3

VS 2010 Ultimate Cold Start: 7 seconds

VS 2010 Ultimate Warm Start: 3 seconds

VS 2008 Pro Cold Start: 2 seconds

VS 2008 Pro Warm Start: <1 second

Word 2010 Professional Plus Cold Start: 2 seconds

Word 2010 Professional Plus Warm Start: <1 second

VS 2010 is slower as the IDE is now WPF based. Disabling fancy effects but keeping hardware acceleration improves VS 2010 UI responsiveness and "snappiness" quite a bit.

  • 0

On a Q9450 processor with a single 7200RPM HDD, Visual Studio 2010:

No plugins - intial load = 8 seconds, subsequent loads = 3 seconds.

Resharper installed - initial = 18 seconds, subsequent = 9 seconds.

The VMWare Virtual Debugger Visual Studio 2010 plugin really kills it for me, that buggy plugin takes my Visual Studio 2010 start-up times to 60-80 seconds.

have you ever opened a web.config file directly in VS2010 or VS2008 just to do a quick edit? external to the solution you are in, just like right click web.config open in VS?... we always have this odd delay, it takes about 1 minute to open the file like it has to think about what to do, after that opens fine and saves fine.... every one of our dev machines repos this... always been an odd behavior, and MS always closes our bugs on it as "by design"

I do that quite often, never had any delays.

  • 0

For me on core i7 box running Windows 7 over a 1Gb network connection VS2010 takes about 20 seconds to start, after which it's fairly quick.

And before seeing this topic I never really paid much attention to how long it took, before now it definitely didn't seem like anything near 20 seconds.

  • 0

Me thinks, given the edit you just made, that you don't understand cold/warm boots.

I'm running an i7 930 @ 4ghz with 12GB of RAM and a Vertex 4.

The difference is likely to do with specific addons and what modules you have installed/enabled.

The "Start Page" web control really smashes load times.

  • 0

Me thinks, given the edit you just made, that you don't understand cold/warm boots.

I'm running an i7 930 @ 4ghz with 12GB of RAM and a Vertex 4.

The difference is likely to do with specific addons and what modules you have installed/enabled.

The "Start Page" web control really smashes load times.

if your referencing me , they are warm boots

also realized this is a bumped thread from 2011.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!