tags:

views:

26

answers:

1

I have WCF client that connects to server in Intranet. The very first call takes significant time and user waits patiently until it completes. Second, third calls are at least 30% faster.

What is the best practice to keep WCF client ready to call? I'm thinking about background thread that pings server from time to time (or may be the very first time application starts) but may be there are better/simpler ways?

Service is IIS6 hosted with wsHttp(Dual)Bindings. Problem is serious with Dual endpoint.

A: 

This behavior could be related to the fact that the application pool in IIS is not loaded into memory when the first request arrives.

Darin Dimitrov
It's hardly so, because I administered IIS not to shutdown pool and observe the delay on every client in organization (there are about ten installations).
Andrew Florko
How about the very first request after the server reboot?
Darin Dimitrov
Thank you for the attention I'll investigate it a bit later
Andrew Florko