http://www.codeproject.com/KB/IP/AsyncSocketServerandClien.aspx?msg=1540676#xx1540676xx
This did the trick!!!!!! No 100% CPU load anymore
I understand the setting, but what on earth then is the default setting, some busy poll loop???
Can't MS sack that programmer for life
Well, looking a bit more on the internet (http://www.iis.net/922/SinglePageArticle.ashx[^] I found this:
"Due to a bug in the Windows Communication Foundation that isn't fixed in Beta 2 a net.tcp request to the net.tcp Listener Adapter service (SMSvcHost.exe) will peg the CPU at 90%. The workaround is to add the following to the file %windir%\WinFX\v3.0\Windows Communication Foundation\SMSvcHost.exe.config:
"socket alwaysUseCompletionPortsForAccept="true""
Apparently this bug isn't just in WCF, but already made his way to XP / .NET 2.0
-- modified at 12:37 Tuesday 20th June, 2006
This did the trick!!!!!! No 100% CPU load anymore
I understand the setting, but what on earth then is the default setting, some busy poll loop???
Can't MS sack that programmer for life
Well, looking a bit more on the internet (http://www.iis.net/922/SinglePageArticle.ashx[^] I found this:
"Due to a bug in the Windows Communication Foundation that isn't fixed in Beta 2 a net.tcp request to the net.tcp Listener Adapter service (SMSvcHost.exe) will peg the CPU at 90%. The workaround is to add the following to the file %windir%\WinFX\v3.0\Windows Communication Foundation\SMSvcHost.exe.config:
"socket alwaysUseCompletionPortsForAccept="true""
Apparently this bug isn't just in WCF, but already made his way to XP / .NET 2.0
-- modified at 12:37 Tuesday 20th June, 2006
이올린에 북마크하기
