61–70 of 85 posts
This is great. I hope they make this available for web apps because we've got 45 second warmup time and CPU spamming due to the massive size of the work the JIT has to do when we deploy. Total pain. I imagine this would help them keep costs down on Azure as well.
This is great. I hope they make this available for web apps because we've got 45 second warmup time and CPU spamming due to the massive size of the work the JIT has to do when we deploy. Total pain. I imagine this would help them keep costs down on Azure as well.
It is possible to precompile web apps already today.
1. Proxy generation (castle) -> IL
2. IL -> Native.
This is great. I hope they make this available for web apps because we've got 45 second warmup time and CPU spamming due to the massive size of the work the JIT has to do when we deploy. Total pain. I imagine this would help them keep costs down on Azure as well.
Larger EF models can have quite an impact.
Also if you use New Relic, it can seriously affect startup time too.
This is great. I hope they make this available for web apps because we've got 45 second warmup time and CPU spamming due to the massive size of the work the JIT has to do when we deploy. Total pain. I imagine this would help them keep costs down on Azure as well.
From my experience, much of an ASP.NET web app's start time is not so much the JIT-ing but before that, when the ASP.NET runtime compiles pages/views (aspx/cshtml etc) into *.cs then DLLs. Pre-compiling can mitigate this. Larger EF models can have quite an impact. Also if you use New Relic, it can seriously affect startup time too.
It takes forever for the JIT to actually compile all code paths in these assemblies.
There's no PDBs in there either. Our domain and NH maps consume 42Mb of that to give you an idea.
It seems the comments area here is full of lots of questions and few answers. Let me try to clear some things up. Lets start with how it currently works... When you create an application or website in C#,F#,VB.NET or any other .NET language you are not really 'compiling' it per se to native code, you are compiling it to an intermediate language called IL - very much like Java byte code. When your application or websi…
Microsoft: "We could speed up your server-side code, but instead we did speed up the slow windows mobile apps that nobody cares about."
here, educate yourself http://msdn.microsoft.com/en-us/library/6t9t5wcf(v=vs.110).a...
http://stackoverflow.com/questions/385841/does-it-help-to-us...
Earlier quoted context omitted.
When I read the OP, I was tempted to scream about bad writing due to lack of context, undefined terminology, and general lack of explanation, not nearly the first time I was tempted to scream at Microsoft's technical writing abilities. Your post provided essentially everything that was missing. But, what the heck is a "Windows store app"? What the heck is "jitter"?
Windows Store Apps are what was once called 'Metro' apps and now termed 'Modern' apps. They are essentially Microsoft's version of apps from iOS app store or Google Play store but focused on Windows 8 tablet and desktops (and as of today, the same apps you develop for these environments can also work on Windows Phone and XBOX One) In the past if you were writing a client side or 'desktop' app for Windows you used C++…
No mention anywhere of ASP.NET. Is this going to help ASP.NET in any way?
It seems the comments area here is full of lots of questions and few answers. Let me try to clear some things up. Lets start with how it currently works... When you create an application or website in C#,F#,VB.NET or any other .NET language you are not really 'compiling' it per se to native code, you are compiling it to an intermediate language called IL - very much like Java byte code. When your application or websi…
How good/reliable is Mono on Linux now? If I knew for sure that people are actually using Mono on Linux robustly and with good performance I would ditch the JVM - as a language/runtime .Net is so much better...
We haven't done many systematic performance comparisons. However, it seems to be the case that whilst Mono still performs worse than .NET in a few areas (e.g. loading new AppDomains), in general there isn't a significant performance difference between running OpenSimulator on Mono and on Windows.
Hopefully the marketing people let them spread it to all of their application types.