Last post Oct 18, 2013 07:08 AM by Illeris
Oct 16, 2013 08:36 PM|hardywang|LINK
The blog post http://blogs.msdn.com/b/wenlong/archive/2010/02/11/why-does-wcf-become-slow-after-being-idle-for-15-seconds.aspx has
a very good explanation in .Net 4.0 (the version I am using) and provided a workaround solution.
Basically the workaround just keeps one thread free. In the sample code provided from blog post, the author used self hosting. Before ServiceHost has been instantiated the workaround
code is executed to hold that free thread.
My question is in the IIS7.5/WAS hosting, what should be the best way to call it?
Oct 18, 2013 06:04 AM|Rajat|LINK
As per my understanding
Once you deployed your WCF service in IIS then as it work on ASP.NET platform which and .NET platform is based ON MTA.
then you don't need to worry about threading stufff.
the only best thing which you can do is use of "USING" in your client application
Oct 18, 2013 07:08 AM|Illeris|LINK
Your issue is an anomaly, not a default situation for most developers (luckyly). Therefore, I'd look to the code and see what could be wrong.
.NET applications do become slow if your memory consumption gets way too high (>90%). This is mostly caused by improper coding practices. Please check the memory consumption and IO consumption of your application.