WCF Performance

Thread pool throttling

http://blogs.msdn.com/b/wenlong/archive/2010/02/11/why-does-wcf-become-slow-after-being-idle-for-15-seconds.aspx

http://social.msdn.microsoft.com/Forums/en/wcf/thread/2dc57a71-6708-4a38-b7a9-8230fdd5675f

Antivirus slowdown

http://social.msdn.microsoft.com/Forums/en-NZ/wcf/thread/dc4a2ee7-fa3b-4ea5-9bf6-1bd6e141954f

Reliable Messaging

http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/5f21fc60-cfe8-4a75-8284-84f414f5fb6c

http://stackoverflow.com/questions/13028717/wcf-is-slow-when-reliable-session-is-on-and-with-burst-async-request

Async/Await

Using Async/Await from .NET 4.0
* Download from http://nuget.org/packages/Microsoft.CompilerServices.AsyncTargetingPack
* License is here http://www.microsoft.com/en-us/download/details.aspx?id=29576

Using TPL to implement APM
* http://blogs.msdn.com/b/pfxteam/archive/2011/06/27/using-tasks-to-implement-the-apm-pattern.aspx

Synchronization Contexts in UI, Console, ASP.NET etc
* http://msdn.microsoft.com/en-us/magazine/gg598924.aspx

When used on UI application, the code after "await" is executed by UI thread by default.  In Console application however, we need special treatments. See:
1. http://blogs.msdn.com/b/pfxteam/archive/2012/01/20/10259049.aspx
2. http://blogs.msdn.com/b/pfxteam/archive/2012/01/21/10259307.aspx
3. http://blogs.msdn.com/b/pfxteam/archive/2012/02/02/10263555.aspx

WCF: Windows Communication Foundation

SelfHosting tutorial

http://msdn.microsoft.com/en-us/library/ms731758.aspx

How to publish metadata when using TCP binding:
1. Inside app.config, create service behavior element (e.g. HelloServiceBehavior)
2. Refer the behavior from service tag (behaviorConfiguration="HelloServiceBehavior")
3. Add endpoint to the service to exchange metadata, use contract="IMetadataExchange".

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <startup> 
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
    </startup>
    <system.serviceModel>
        <behaviors>
            <serviceBehaviors>
                <behavior name="HelloServiceBehavior">
                    <serviceMetadata policyVersion="Policy15" />
                    <serviceDebug includeExceptionDetailInFaults="true" />
                </behavior>
            </serviceBehaviors>
        </behaviors>
        <services>
            <service behaviorConfiguration="HelloServiceBehavior" name="HelloService">
                <endpoint address="net.tcp://localhost:8080/hello" binding="netTcpBinding"
                    bindingConfiguration="" name="HelloService" contract="IHelloService" />
                <endpoint address="mex" binding="mexTcpBinding" contract="IMetadataExchange" />
            </service>
        </services>
    </system.serviceModel>
</configuration>

Using Async/Await

http://blogs.msdn.com/b/endpoint/archive/2010/11/13/simplified-asynchronous-programming-model-in-wcf-with-async-await.aspx

Async Cancellation/Progress is not supported

http://social.msdn.microsoft.com/Forums/en-US/async/thread/b1353952-ce52-4af7-b6ec-f792bef28566/

Enabling trace

http://stackoverflow.com/questions/4271517/how-to-turn-on-wcf-tracing

Encoding

netTcpBinding uses binary encoding and transport security, which delivers better performance.

Following URLS will help to get more information

http://msdn.microsoft.com/en-us/library/cc949026.aspx

http://msdn.microsoft.com/en-us/library/ms730879.aspx

Recovering from Fault connection

Client proxy cannot be reused: http://stackoverflow.com/questions/1241331/recovering-from-a-communicationobjectfaultedexception-in-wcf
Solution: http://bloggingabout.net/blogs/erwyn/archive/2006/12/09/WCF-Service-Proxy-Helper.aspx

Classes

NetTcpBinding: http://msdn.microsoft.com/en-us/library/system.servicemodel.nettcpbinding.aspx

ServiceContractAttribute: http://msdn.microsoft.com/en-us/library/system.servicemodel.servicecontractattribute.aspx

OperationContractAttribute: http://msdn.microsoft.com/en-us/library/system.servicemodel.operationcontractattribute.aspx

ServiceBehaviorAttribute: http://msdn.microsoft.com/en-us/library/system.servicemodel.servicebehaviorattribute.aspx

Performance

Concurrency and Throttling combinations http://www.codeproject.com/Articles/89858/WCF-Concurrency-Single-Multiple-and-Reentrant-and

Timeout

Open/Close/Send/Receive/Operation: http://cs.gogo-asp.net/blogs/libaty/archive/2009/11/02/WCF_6730E930A630F330C930C830EA30C330D7306E30BF30A430E030A230A630C830245092302D8A9A5B59308B306B306F30_.aspx

Detecting Disconnected Clients

http://stackoverflow.com/questions/665473/how-to-handle-wcf-client-disconnect
http://stackoverflow.com/questions/5338842/detect-socket-disconnect-in-wcf

Reliable Messaging

Need to turn-off or set level to Message Security for Bindings (doesn't work if the level is set to the default Transport level)

Working case

- Server not available during the first connection

- Network cable is blipping

Not working case

- Server is down and restarted

WCF and WebSocket

WebSocket only available in Windows8 ? (http://msdn.microsoft.com/en-us/library/system.servicemodel.nethttpbinding.aspx)
http://msdn.microsoft.com/en-us/library/hh977020.aspx
http://www.codeproject.com/Articles/341413/What-s-new-in-WCF-4-5-WebSocket-support-Part-2-of

Performance Tuning

http://blogs.msdn.com/b/dmetzgar/archive/2011/05/04/wcf-scales-up-slowly-with-bursts-of-work.aspx

Multiple Contract per Service

See http://stackoverflow.com/questions/334472/run-wcf-servicehost-with-multiple-contracts

Example

http://www.codeproject.com/Articles/87510/WCF-by-Example-Introduction

Configuration Schema

http://msdn.microsoft.com/en-us/library/ms731734.aspx

Network TCP/IP Packet Capture

http://codezine.jp/article/detail/125

Linking Boost DLL on Windows

http://stackoverflow.com/questions/2520234/how-to-link-to-dynamic-boost-libs

.NET Async Await

* Performance consideration: http://msdn.microsoft.com/en-us/magazine/hh456402.aspx
* Comparison with old patterns: http://msdn.microsoft.com/en-us/library/jj152938.aspx

,NET timers

Comparisons: http://msdn.microsoft.com/en-us/magazine/cc164015.aspx

Note that System.Timers.Timer and System.Threading.Timer by default call your timer event handler on a worker thread obtained from the common language runtime (CLR) thread pool.

	System.Windows.Forms	System.Timers	System.Threading
Timer event runs on what thread?	UI thread	UI or worker thread	Worker thread
Instances are thread safe?	No	Yes	No
Familiar/intuitive object model?	Yes	Yes	No
Requires Windows Forms?	Yes	No	No
Metronome-quality beat?	No	Yes*	Yes*
Timer event supports state object?	No	No	Yes
Initial timer event can be scheduled?	No	No	Yes
Class supports inheritance?	Yes	Yes	No
* Depending on the availability of system resources (for example, worker threads)