ExecuteRequestHandler spent most of the time

Question

I'm working on some performance related tasks and using new relic to diagnose first.
Here is what I have got

New Relic Screenshot

I'm wondering is it possible to improve on the ExecuteRequestHandler part? Any help will be appreciated.

Thanks!

Hey, did you figure this out? – Benjamin Gruenbaum Jan 14 '16 at 08:48 — Benjamin Gruenbaum, Jan 14 '16 at 08:48
I am also looking into this, did you find anything out – runxc1 Bret Ferrier Aug 17 '16 at 17:31 — runxc1 Bret Ferrier, Aug 17 '16 at 17:31
lol not sure, but feels like requests get queued... – Ryan Chu Aug 18 '16 at 00:03 — Ryan Chu, Aug 18 '16 at 00:03
has anyone found out how to see deeper into those segments? – Jtello Jun 20 '17 at 20:59 — Jtello, Jun 20 '17 at 20:59
I'm also facing issue. Has anyone got any resolution ? – Heera Jaiswal Jun 29 '17 at 12:07 — Heera Jaiswal, Jun 29 '17 at 12:07
I'm also facing same issue – Jignesh Hirpara Jun 13 '18 at 06:15 — Jignesh Hirpara, Jun 13 '18 at 06:15

score 0 · Answer 1 · answered Aug 25 '23 at 06:01

ExecuteRequestHandler is not a thing you can improve on it's own. To improve it you need to improve the code that is actually being executed.

So you need to trace your application logic to determine what is taking so long. New Relic does have a .Net Agent API that you can use to help with this, but without having visibility into what your code is doing New Relic can really only help us to identify endpoint performance and to isolate network and host latencies from the execution of your business logic.

ExecuteRequestHandler spent most of the time

1 Answers1

Linked