4 ms·
The CLR is quite terrible at small programs, as you're seeing. That being said, the huge "Image" section doesn't have to be as big as you're seeing. If you loo
by shakna 9y ago
The CLR is quite terrible at small programs, as you're seeing.
That being said, the huge "Image" section doesn't have to be as big as you're seeing. If you look at the breakdown [0], then you can see some debugging, in the form of "TraceDLL". He also mentions that the four biggest memory eaters: System.Private.CoreLib.dll, coreclr.dll, clrjit.dll and CoreRun.exe are probably bigger than normal, because he's using a debug version of the CLR.
Outside those five, every other piece of memory is shared, which changes how you see its allocation.
I'd expect it'd change a measurable amount, but as before... The CLR is best when handling bigger programs, where JITing can actually make sense.
[0] http://mattwarren.org/images/2017/07/Image%20Memory%20Usage.png http://mattwarren.org/images/2017/07/Image%20Memory%20Usage....
- matthewwarren 9y ago> The CLR is quite terrible at small programs, as you're seeing. Yeah that's a good point, I deliberately chose to do a 'Hello World' app to make it easier to see what the CLR itself was doing, so that there was the bare minimum of non-essential things going on (that would make it harder to see). But the side-effect is that it does show the CLR in a bad-light, people expect 'Hello World' apps to be a bit 'slimmer'