A group blog from members of the VB team
Looking for another reason to upgrade to 2008? How about performance! In addition to making tasks easier for you from release to release, another way we can save you time and make you more productive is by making the product faster! This is a goal we are very commited to on the VB team, and for which we have dedicated an entire virtual team for the Orcas release. Take a look at the stats below to see some interesting improvements.
[**DISCLAIMER: The data posted here is what I have observed from comparing 2 runs in our internal labs. These are my observations using two large customer solutions on a specific machine. Some people will have faster systems and some will have slower. Also, the work required for each operation will differ based on your solution. Thus, your results may be better or worse. The interesting thing is to look at the improvement between versions on identical hardware. I am posting this data to try and give you a general idea of the changes - but these numbers are by no means meant to be used as an industry standard.
For those interested, here's some data on the solutions and machine that I used... One solution contains 29 projects and 2772 files, with xml comments on all methods and types. The other solution used contains 783 files. The machine has the following specs: Dual Core Pentium-D - 3.0GHz, 1GB RAM, 10K RPM HD. OS=XP. These are one of many machine specifications that we use for our internal performance testing.]
Is there another scenario you're interested that you don't see above, where you continue to experience performance lags in your regular usage of the product? Please send in repro steps so we can take a look! (firstname.lastname@example.org)
Other interesting VB2008 Performance content to check out is listed below:
Microsoft, ha publicado una interesantísima lista de comparaciones entre VB 2005 y VB 2008. En esta lista
You must have a super computer to gain that much performance VS2005 and 2008 alike :-)
"You must have a super computer to gain that much performance VS2005 and 2008 alike :-)"
or simply the project is "hello world" :P
well i'm thrilled that it's faster, vb2k5 really slows me down on large projects, and i have to break my solution into diffrent projects to compile faster.
shouldnt the header say VS not VB?!?
In an interesting blog , about how VB2008 Outperforms VB2005, by Members of the VB team in Microsoft
yes, I still think it should be 'perf of Visual Studio using VB' as these are Visual Studio actions while using VB as your dev language. If we are talking about VB performance then I think its reasonable to expect items detailing language performance. The only reason I made the observation is it appeared on my rss feed and was misled by the header.
so it was just a thought and no reason to respond with an all high and mighty comment...
This is simply wonderful. VB has stood the test to times. Though it started as a common language - easy to develop winforms... it has graduated a lot in the .net world.
The % column is wrong - if B is 99.4% faster than A then it would be almost twice as fast. You are showing 164.25x hence you should be saying 16425% improvement. [Or just drop the % column altogether as the x column is clearer]
I thought the Non Object Oriented VB was dead. Is this the OO one?
Is the syntax of VB as clean as Java? The Java Swing GUIs are really fast too and have so many free components that are a piece of cake to use.
I agree with Gary - the % column is wrong, and misleading.
The 'x times faster' column has been calculated as:
while the '% faster' has been calculated as:
1 - (new/old)
Stick to one consistent calculation technique.
That said, glad to see the lovely perf improvements.
I'm running a 1.8 MHz claptop with 1GB RAM with 7 GB free disk space.
My drive thashes like crazy when running VS2008 and sometime just getting a content sensitive menu to pop up takes 45 seconds.
Quite often, for a minute at a time, the IDE just appears to be too buy to respond to me.
Does VS2008 really need more memory than 1GB? That is the official RECOMMENDED amount.
I thik the last column would make more sense to folks if displayed as "% time taken" and was 1- current value, eg: the first entry would be 0.6%, andthe last one would be 89.2%
The % percent faster column is backwards:
Twice as fast is 200% faster, not 50%!!!
>>My drive thashes like crazy when running VS2008 and sometime just getting a content sensitive menu to pop up takes 45 seconds.
Chad, your system is paging it's brains out. What else are you running? SQL Server?, etc.
I've seen the VB Compiler bug (or one that resembles it) in a simpler single assembly project. In the designer I add & edit stuff but it doesn't show in the complied version (or after hitting F5). Its as if something in RAM did not get set and the JIT doent recognize that certain edited areas need to be re-compiled. After saving everything, I crossed my fingers, unloaded the guilty form from the project, exited, reopened & reloaded the form. In that ocassion it worked!
Also if you place the cursor past the End Class line in a class & then Ctrl-PgUp to go to the top of the last Sub or method, you get a send error to MS prompt, although I've not lost any data.
Other than that it looks pretty good and I'm still using it.