First of all, we would like to thank all XF.Server users and especially Mash for his performance considerations.

XF.Server is positioned as a component that should outperform standard .NET classes and we did it except for HttpListener(which uses kernel mode listener - http.sys).

According to our benchmarking we have the following results(in performance order).
1. HttpListener (both with cached and dynamic page data)
2. XF.Server
3. TcpListener
4. .Net Socket Async
5. Dart PowerTCP Socket (3rd party component)

NOTE:
1. HttpListener shows high performance if it is a real request(can accept connection and read data from it) which is the most case. But if there are only stale connections(clients connected but didn't send data) then it works bad.
2. HttpListener can only be used to process http requests(actually we suggest that), but if you need to process custom protocol over TCP/IP then XF.Server is the best choice.

Sources of the demo servers used to test performance and detailed test results will be provided in a few days.

Thanks,
Kodart Technologies