Tuesday, April 4, 2017

Low latency, high throughput TCP

For C++ devs looking to push the envelope with respect to latency and throughput when using TCP, checkout mTCP! https://github.com/eunyoung14/mtcp

Tuesday, March 14, 2017

Async and await on the JVM

For those interested, this is a very very big deal.  Many of us from the C# side of things have been longing for async await on the JVM.  While I realize Quasar has been around for a while, Kotlin has a much more elegant compiler supported approach.  This is awesome!!

https://blog.jetbrains.com/kotlin/2017/03/kotlin-1-1/
https://github.com/Kotlin/kotlin-coroutines
https://github.com/Kotlin/kotlinx.coroutines

Given Kotlin will support native code compilation in the future on everything from IOS, Android to the PC, the possibilities for having a single build which targets all platforms are getting closer.

Saturday, June 21, 2014

Intel, Xeon, FPGA

I've been waiting years for an on die FPGA!

http://www.extremetech.com/extreme/184828-intel-unveils-new-xeon-chip-with-integrated-fpga-touts-20x-performance-boost

Time to brush up on the Verilog.  Combine with C++ and mcorelab, we'll finally be able to really cook!  High throughput message routing based on topic paths or tag/value pairs will now be possible.  The line between network switch and application is finally starting to blur, and high throughput applications will be easier to build with commodity servers.

Thursday, June 12, 2014

Mcorelab - Mcoreweb bench numbers

Quick correction, numbers below are for Haswell with AVX2.

These are unofficial numbers, mileage may vary depending on your hardware.  Still pretty amazing.  With a low enough update rate I'd reckon one could get millions of websocket users on a single server!

http://www.mcorelab.com

test setup and some performance numbers of mcoreweb server (number reported are single server performance):
- server: dual E5-2690 with Intel 10GbE (X520).
- client:  multiple client nodes generating load, total of 100,000 concurrent client sockets/connections.
- server answer each request message with a response message.
- message payload size=64Byte, so the test is the raw message/request handling capacity, rather than limited by PHY -- our software can easily saturate 10Gbit with just moderate message size)

Windows 2012/2008-R2:
1). sample server implemented on the mcoreweb/TCPserver layer:
using 2 core on the server: 1.5 Million/second,
using 4 core on the server: 3.3 Million/second
using 8 core on the server: 5.9 Million/second

SSL (AES encrypted):
using 4 core on the server: 1.35 Million/second
using 8 core on the server: 2 Million/second
(If using Intel newer gen Ivybridge CPU, SSL performance is much better. here the result is limited SandyBridge CPU which is without the new AVX2 instructions.)

2). sample server implemented on the mcoreweb/websocket layer:
2 core: 1.48 Million/second
4 core: 2.56 Million/second
8 core: 5.55 Million/second

Secure Websocket (AES encrypted):
4 core: 0.95 Million/second
8 core: 1.99 Million/second

Redhat Linux 6.4:
1). sample server implemented on the mcoreweb/TCPserver layer:
using 2 core on the server: 1.8 Million/second,
using 4 core on the server: 3.4 Million/second
using 8 core on the server: 6.1 Million/second

SSL (AES encrypted):
using 4 core on the server: 1.13 Million/second
using 8 core on the server: 2.1 Million/second

2). sample server implemented on the mcoreweb/websocket layer:
2 core: 1.43 Million/second
4 core: 3 Million/second
8 core: 5.45 Million/second

Secure Websocket (AES encrypted):
4 core: 0.99 Million/second
8 core: 1.75 Million/second

How to handle millions of concurrent websocket connections from web browsers

These are unofficial numbers, mileage may vary depending on your hardware.  Still pretty amazing.  With a low enough update rate I'd reckon one could get millions of websocket users on a single server!

http://www.mcorelab.com

test setup and some performance numbers of mcoreweb server (number reported are single server performance):
- server: dual E5-2690 with Intel 10GbE (X520).
- client:  multiple client nodes generating load, total of 100,000 concurrent client sockets/connections.
- server answer each request message with a response message.
- message payload size=64Byte, so the test is the raw message/request handling capacity, rather than limited by PHY -- our software can easily saturate 10Gbit with just moderate message size)

Windows 2012/2008-R2:
1). sample server implemented on the mcoreweb/TCPserver layer:
using 2 core on the server: 1.5 Million/second,
using 4 core on the server: 3.3 Million/second
using 8 core on the server: 5.9 Million/second

SSL (AES encrypted):
using 4 core on the server: 1.35 Million/second
using 8 core on the server: 2 Million/second
(If using Intel newer gen Ivybridge CPU, SSL performance is much better. here the result is limited SandyBridge CPU which is without the new AVX2 instructions.)

2). sample server implemented on the mcoreweb/websocket layer:
2 core: 1.48 Million/second
4 core: 2.56 Million/second
8 core: 5.55 Million/second

Secure Websocket (AES encrypted):
4 core: 0.95 Million/second
8 core: 1.99 Million/second

Redhat Linux 6.4:
1). sample server implemented on the mcoreweb/TCPserver layer:
using 2 core on the server: 1.8 Million/second,
using 4 core on the server: 3.4 Million/second
using 8 core on the server: 6.1 Million/second

SSL (AES encrypted):
using 4 core on the server: 1.13 Million/second
using 8 core on the server: 2.1 Million/second

2). sample server implemented on the mcoreweb/websocket layer:
2 core: 1.43 Million/second
4 core: 3 Million/second
8 core: 5.45 Million/second

Secure Websocket (AES encrypted):
4 core: 0.99 Million/second
8 core: 1.75 Million/second

Tuesday, June 10, 2014

The grandaddy of c100k

This does a great job explaining the scaling issues in server side programming.  Lots of technical concepts, but laymen should also be able to get the big picture.

The original c10k article