.net - Managed Debugging Assistant(MDA) jitCompilationStart usage -
i'm trying optimize cold startup time of winforms application.i've ngen'ed assemblies still see jit invoked. i've enabled mda's jitcompilationstart , see runtime exceptions mda saying causing invocation of jit.
my question - what? see list of suggested debuggers. if choose sthm list - see nothing in vs. app continues execute , that's all. how can info part of app invokes jit?

i've enabled jitcompilationstart in debug->exceptions -> managed debugging assistants:

that mda meant debugger attached when jitter starts. requirements registered unmanaged debugger capable of debugging c++ code source code jitter. have first requirement met, vs20120 , vs2012 have excellent unmanaged debuggers. latter 1 rather hard 1 mere mortals , me. entire scenario interesting microsoft sdets.
clearly on wrong path diagnose cold start delays. in more 1 way, jitter warm start detail. cold starts dominated time required disk find assembly files. using ngen in fact don't want do, doubles number of files need found. improve warm start times.
there 3 solutions cold start delays. use less assemblies, ilmerge can help. use faster disk, ssd helps lot. , cheat, start small do-nothing .net program @ login time gets assemblies loaded file system cache. automatic after user has started .net app while, windows prefetcher learns , preloads dlls. hard notice, other customer stopping complain after while.
Comments
Post a Comment