Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve seen several articles on warming up a WCF service when it is hosted in IIS (that is, pre-loading caches, loading plug-ins etc – basically all the expensive stuff you don’t want your users to be hanging around for when they issue their first request), but I haven’t seen anything equivalent for when WCF is self-hosted in a .NET service.
Has anyone been able to achieve this?
If you’re hosting your service, than you can create a client (i.e., using
ChannelFactory<T>) to the service right after you call ServiceHost.Open and issue a “ping” request; that way if the service implementation is doing some heavy loading, it can happen right then, instead of when the first “real” client request arrives.