First Web API session request is very slow

Question

I'm writing an ASP.NET Web API application hosted on IIS7 (no special configuration).

My problem is that for each first request (on a new machine/new browser/after a while...) there is a long delay - even on requests that return constants!

I've read about "warming up" scripts but it's not the issue here. It seems like the web server is trying to create a session and it takes very long time. Any suggestions?

EDIT

I think the delay is caused by worker-process creation for each new session. Now the question is why is it so slow, and why doesn't the web server reuse living worker-processes to serve requests?

I have configured the application pool to limit worker processes to 5 with no timeout (set to 0). This caused the first five sessions to be slow on first requests (which I can live with) and now the worker processes are alive. But surprisingly, from time to time, the request is slow again!

What exactly happens? Is this first request so slow after some time, from new browser window, from new machine, with all those conditions or with any of them? — Konrad Kokosa
any of them. on my own PC it doesn't happen so I guess it's an IIS configuration issue — Niro
every day in CRM and SharePoint we sense very delays on starting web applications is this useful for SharePoint sites ??? — saber tabatabaee yazdi

Darin Dimitrov Darin Dimitrov · Accepted Answer · 2013-11-24T09:44:57

If you are using Windows Server 2008 R2 you could configure the Auto-Start feature on the Application Pool. Also in the properties of the application pool you should disable it from being recycled at regular intervals. Bear in mind though that while this will limit the slowness, the application pool could still be recycled by IIS. With the Auto-Start feature it will be loaded again automatically in memory, but the code in your Application_Start will be executed on the next request. So you could still observe some slowness.

First Web API session request is very slow

2 Answers