CLR Updates in .NET Framework 3.5 SP1
Kevin Frie, development lead for core parts of the CLR recently posted about what CLR updates that come in 3.5 SP1....
- NGen infrastructure rewrite: the new infrastructure uses less memory, produces less fragmented NGen images with much better locality, and does so in dramatically less time. What this means to you: Installing or servicing an NGen image is much faster, and cold startup time of your NGen’ed code is better.
- Framework Startup Performance Improvements: The framework is now better optimized for startup.
- Better OS citizenship: We’ve modified NGen to produce images that are ASLR capable, in an effort to decrease potential security attack surface area.
- Better 32-bit code quality: The x86 JIT has dramatically improved inlining heuristics that result in generally better code quality, and, in particular, much lower “cost of abstraction”.
Comments
Anonymous
August 19, 2008
PingBack from http://blog.kantikalyan.com/links-august-19th-2008/Anonymous
August 19, 2008
For those that don't read the article and the linked connect request (https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=93858&wa=wsignin1.0) this appears to NOT be a feature of the x64 JIT (previously superior to the x86 one in every benchmark I ever tried) While I applaud the changes made I am becoming increasingly unhappy with Microsoft's lack of priority with the 64bit code. The people who care about performance will almost certainly be on (native) 64bit.Anonymous
August 20, 2008
With these improved inlining heuristics, do the same requirements apply as before such as the ones listed here? (http://blogs.msdn.com/ericgu/archive/2004/01/29/64717.aspx) I'm mainly curious as to the exception handling block rule.Anonymous
August 20, 2008
Please deliver the .NET 2.0 SP2 bits for Windows 2000 SP4 in a separate service pack because .NET 3.0 and above can't be installed on that OS.Anonymous
August 20, 2008
Please don't waste time on Windows 2000. It is 8 years old, which is a long time in compter years (like dog years). If you're running Windows 2000, it's time to upgrade.Anonymous
August 20, 2008
And XP is 7 year old. It all depends on whether MS chooses to support it or not. And Windows 2000 is not yet out of support and runs fast on slower machines.Anonymous
August 20, 2008
What I have disliked most about the VS 2008 Sp1 is the fact that it requires more than 4 GB of space to be installed. i do not have that much of space in the drive and some how I will not be able to get that much space. i am not sure what to do and how to install the sp1Anonymous
August 21, 2008
My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. The Web Developer Tools Team announced the release of the Dynamic Data Wizard Preview 0806 for VS 2008 SP1 . US ISV Developer EvangelismAnonymous
August 29, 2008
Please deliver the .NET 2.0 SP2 bits for Windows 2000 SP4 in a separate service pack.Anonymous
August 29, 2008
Храните Ваши вина в винных шкафах и винных погребах! Незнаете где купить? .NET 2.0 SP2 bits for Windows 2000 Только у нас большой выбор винных шкафов и винных погребов.Anonymous
September 09, 2008
First of all, I appreciate performance improvements, BUT doesn't the policy of publishing service packs disallow to break compatibility with existing applications? We are using .NET Framework 3.5 and Dotfuscator (which seems to be "microsoft-approved" obfuscator - community edition is attached to Visual Studio) - and now our application explodes at every customer which installs SP1. All because CLR team has broken reverse compatibility of independent virtual method overrides renaming. I mean situation that virtual method override has different name than base method it was overriding what was perfectly ok in pre-SP1. Of course guys from Preemptive, 2 months ago, introduced new feature allowing to disable this override renaming (what of course solve the issue), but we have a lot of non-forward-compatibile obfuscated binaries sent to our customers and now we will be receiving complaints when people install SP1. Thanks guys!Anonymous
September 11, 2008
【原文地址】 CLR Updates in .NET Framework 3.5 SP1 【原文发表日期】 19 August 08 07:57 Kevin Frie ，CLR核心部分的开发主管最近发布了一篇帖子Anonymous
September 17, 2008
@ Marcin THanks for your comments Marcin We’re sorry you’re running into problems. This looks like a known issue in 3.5 SP1 and we’re working on a fix. Can you send an email address at which we can reach you and we’ll work with you to see if this is the issue we’ve already seen.Anonymous
September 27, 2008
I cannot for the life of me see a technical workaround but to reJIT and do obfuscation again regarding that specific problem. So, tough, let them include auto-update to their apps.. It is FAR, FAR, more critical to fix the x64 issue for structs and lack-of-inlining. Didn't MS learn from Cutler's anger before? There are stacks of articles criticing both the JIT and the C# compiler, clearly demonstrating lack of basic compiler implementation skills in 21st century. That is simply unacceptable as is the performance of WPF, WinForms/GDI+ and much more. First thing first, you have best guys in the field to do this and you beat Sun with a better Java VM for years. Who on earth is the product manager of that messy approach? The JIT still has a long way to go to catch up with Java's optimizations, so why keep delaying the work and fixes?Anonymous
October 20, 2008
Наши специалисты спроектируют и оборудуют винный шкаф и винный погреб , максимально эффективно используя пространство Вашего загородного дома или офиса.Anonymous
February 03, 2009
Otherwise known, as "Return of the Giant Hogweed " Once upon a time , .NET was so new that there wasn't a Visual Studio .NET yet (the beta crashed every 5 minutes so you couldn't use it even if you wanted to), no books, few blogs and one had