Your official information source from the .NET Web Development and Tools group at Microsoft.
Visual Studio 2010 Beta2 is out and we at the Web Development Tools team are pleased to let you know that we have fixed a lot of the performance issues from Beta1. It took a considerable amount of time and effort but we feel it was well worth it. We would like to thank the community for your feedback and in helping us identify a lot of these issues.
There has been some good improvements to Add Reference dialog, first switch to design view etc. Please try using Beta2 and let us know if you find any of the Web Scenarios to be particularly slow. We would like to hear your issues and concerns around performance for Web Scenarios.
You can help make the product better by providing us with early feedback. If you encounter a performance issue please respond via comments section of this blog or you can reach us at vwdperf-at-microsoft-dot-com.
Here are the list of information that can help us with to narrow down the issue.
1. What is the time taken in Visual Studio 2008 SP1 for this action? 2. What is the time taken in Visual Studio 2010 for this action? 3. Can this be reproduced consistently in Visual Studio 2010? 4. Do you have a ASP.NET Website or a ASP.NET Web Application Project? What is the size of this Website or Web Application Project? 5. Is it C# or VB? 6. Is it a 4.0 , 3.5 or a 2.0 App? 7. Do you have other applications running on the box? If so what are they? 8. Machine configuration.
SDET| Web Development Tools
aspnet_compiler.exe is extremely slow, and has been for the last 3 iterations of Visual Studio. Even for a relatively small website (20 pages), running aspnet_compiler.exe causes my hard drive (backed up by 12 GB system of RAM) to grind away for what seems forever. I think this application needs some serious attention to performance improvements.
Yes, I agree. Web_deployment projects take a looong time. Totally reproducible, because it's never been fast.
Are you using Web Deployment Projects with VS 2008 or are you using aspnet_compiler.exe independently...?
The reason I am asking is coz there is no Web Deployment Projects for VS 2010 available yet...
I cannot replicate what Mike is saying; I've installed VS2010 and find the build time for a web application is as quick as VS2008 was.
I'm using nothing fancy a E8400, 4GB, SATAII, Windows 7 and that's worked with 2005,2008 and now 2010 without issues. In fact I find a publish locally or remotely much quicker under 2010 than 2008 - which always seemed to bog down on a network publish.
I've had VS2010 close once on me since using it but then a B2 is never going to be 100% stable.
Steve, It is great to hear that you are not facing the issue and actually are finding improvement in th epublishing for VS 2010 as compared to VS 2008... We do indeed have a brand new FTP stack in there so hopefully it should be better...
I am not sure why Mike is facing the issues, hopefully we will track them down soon...
This is a great news. I am damn sure the memory leak problems we had before will be fixed in this .
We did some quick tests on our team & below are the results..
On the same machine, using a web site containing 10 .cs files and 15 .aspx files.
• VS10 : 4.503 seconds
(Average over 4.45 4.389 4.67)
(Manually measuring time when I select Build Web Site, to time when VS shows “Build succeeded”)
• 4.0 aspnet_compiler: 5.67 seconds
(Average over 5.79 5.72 5.5)
• 2.0 aspnet_compiler: 4.85 seconds
(Average over 4.88 4.735 4.929)
Is this the kind of data that you are seeing... If you would like to discuss more on email then drop me a line at email@example.com
As a whole, Visual Studio 2010 is painfully slow compared to Visual Studio 2005.
I havn't tried to use VS 2010 locally, so I don't know how fast it is in that kind of situation. But over the network every action - like opening a file, adding files to the project, and not to mention debugging, takes a number of times longer time than in VS 2005.
When debugging, every image on the site comes up one at the time and a page that normally is rendered instantly when debugging in vs 2005 takes about 5-10 seconds to be delivered to the browser.
Publishing a small Web Project (about 10 pages, 40 small images, and 10 dll:s) takes anywhere between 2 and 6 minutes (compared to ~10-20 seconds with VS 2005).
Some completing information:
1 & 2:
VS 2005: Opening the project: 3 seconds
VS 2010: Opening the project: 10 seconds
VS 2005: Saving the project with no changes: Instant
VS 2010: Opening the project: 2-3 seconds
VS 2005: Including 8900 files in the project: About 90 minutes
VS 2010: Including 8900 files in the project: About 30 minutes (Alot faster, but contrary to vs 2005, it freezes the redrawing during that time, leaving you to wonder wether it has crashed or not)
VS 2005: Time from hitting the play-button, to first page fully loaded: 9-14s
VS 2010: Time from hitting the play-button, to first page fully loaded: 19-26s (and since the page takes 7-9s longer to load in itself, compiling and starting the debug takes about the same time, it's the deliverence of the page that's MUCH slower with VS 2010)
VS 2005: Page reload during debug, litte graphic: <0,1s
VS 2010: Page reload during debug, little graphic: 7-9s
VS 2005: Page reload during debug, much graphic: 1,5 - 2s
VS 2010: Page reload during debug, much graphic: 27-31s
Compile time with no changes: Equal
3. Can this be reproduced consistently in Visual Studio 2010?
4. Do you have a ASP.NET Website or a ASP.NET Web Application Project? What is the size of this Website or Web Application Project?
See my previous message
5. Is it C# or VB?
6. Is it a 4.0 , 3.5 or a 2.0 App?
7. Do you have other applications running on the box? If so what are they?
Doesn't make any difference (I've tried), but yes, generally alot of them just like all Web Devellopers (Right now, Outlook, Windows Explorer, Trillian, SQL Server Management Studio 2005, 2x Remote desktop, 3x VS 2005, Photoshop CS 4, IE, Chrome, Notepad)
8. Machine configuration.
Vista x64, Core 2 Duo @ 2,66 Ghz, 4 GB memory, 500 GB 7200 RPM Harddrive, 100Mbit network
Publishing is done through NetBIOS over TCP/IP to a machine with Windows Server 2003.
I found out why the debugging went so slow in VS 2010. By setting IE as the default browser instead of Chrome, the debugging is just as fast in VS 2005 as it is in 2010 (2005 always uses IE no matter what browser i default, but VS 2010 respects your default browser settings).
But the question is - why is debugging in Chrome SO much slower than in IE, when Chrome really is the faster browser of the two?
I also tried debugging in FF from VS 2010. When using Firefox, VS 2010 freezes for about 2 minutes before launching the browser (Windows warns about VS 2010 not responding), but once the browser is started the pages loads about as fast as in IE. Firefox takes ~1 second to start when not running it form VS 2010.
So it seems VS 2010 has some major issues with other browsers...
well, i have a win7 with 3G ram and core2duo 2.6 mh
the VS 2010 is slower than 2008 in :
- opening the solusions
- loading files
- openning dialog boxes for the first time after lunching the VS
- laoding the toolbox
- and editing the text in the source code
maybe the reason behind that is the graphics ? but i have 512mb ATI HD4570 VGA Card
or maybe its because the VB is Beta 2
will we will see the final
thanks for all
I'm interested in why you might be seeing other browsers take 2 minutes to start when you start debugging. Can you email me at johndund at microsoft dot com and I can possibly help diagnose this for you?