问题
I'm performance profiling an asp.net web application, on a load of 20 users per second. 20 users are basically crippling the application and nothing it loading.
I'm using the RedGate performance profiler, and I'm not sure what to make of it.
12% of the time is spent in my code (which I can dig in to and improve) but 88% of the time is spent in
System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, int flags)
..I've not a clue what this is (well, I'm fairly sure it's something to do with IIS7...), and tackling a site that's not able to cope with 20 users a second, at 88% of the time taken, this seems like a good place to start.
Any ideas anyone?
回答1:
ProcessRequestNotificationHelper is simply the entry point for your profiling tool to capture data. Dynatrace, like RedGate, defines it as the entry point where their ASP.Net Sensor can begin tracing incoming requests in the ASP.Net pipeline.
https://community.dynatrace.com/community/display/DOCDT60/ASP.NET+Sensor
来源：https://stackoverflow.com/questions/15545025/performance-profiling-asp-net-what-is-processrequestnotificationhelper