Comments
Sort by recent activity
That's a bummer. Do you know if the .NET profiling API exposes more details about the JITing? Any chance those details could be added to a future version of ANTS?
I know that the application I am testing does not use any NGEN'd assemblies (assuming that's the only way to "create" native images; my .NET knowledge isn't really deep). We do use a background thread and use Reflection's LoadAssembly() to pre-JIT DLLs we will be using later in the application and store it in an array. And this works beautifully at runtime. But profiling seems to consider all of that logic as unJITed everytime we grab an assembly from that runtime cache and so it skews our profiling results.
Chris / comments
That's a bummer. Do you know if the .NET profiling API exposes more details about the JITing? Any chance those details could be added to a future version of ANTS?
I know that the application I am...
Another thing I noticed was that the application uses Reflection and calls Invoke on the objects that keep on getting JITed. When I run this code without profiling, I don't see a noticeable performance hit like I do when running ANTS. When I use the Profiler, it seems to be JITing all the time.
I am testing compiling the application to have direct references to the DLLs that normally get loaded using Invoke. But I still wish I could find out more data about What is being JITed and When so I have a better understading of why I see all that JIT time.
Chris
Madison, WI / comments
Another thing I noticed was that the application uses Reflection and calls Invoke on the objects that keep on getting JITed. When I run this code without profiling, I don't see a noticeable perfor...