There is the cost of starting up, and then when processing reaches a stub of code that hasnt been jit'd yet, it has to jit it. But once thats all taken care of, its very fast.
There are ways to avoid the startup costs though. The framework includes a tool called NGen, which precompiles the il for the machine its run on. That should help with start times.
.NET apps eat up more memory initially, because you have the overhead of the clr, and it also reserves a large chunk of memory for the app.
Warren hit it on the head. Most slow .net apps are due to poor usage, or abuse even..
My 2d library is written in c# using opengl, and the performance is just great :)
There are ways to avoid the startup costs though. The framework includes a tool called NGen, which precompiles the il for the machine its run on. That should help with start times.
.NET apps eat up more memory initially, because you have the overhead of the clr, and it also reserves a large chunk of memory for the app.
Warren hit it on the head. Most slow .net apps are due to poor usage, or abuse even..
My 2d library is written in c# using opengl, and the performance is just great :)