Created
February 24, 2012 15:51
-
-
Save rrnewton/1901698 to your computer and use it in GitHub Desktop.
Current performance (latency) of different network-transport backends
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| This is the average latency as measured by a single trial run of 100K ping/pongs with several different transports. | |
| PingTCP: 7.34s >80%CPU | |
| PingTCPTransport: 19s ~60%CPU | |
| PingPipes: 6.36s >=100%CPU | |
| The machine is a 3.1 ghz Intel Westmere (Dell workstation) running RHEL 6.2. | |
| The PingTCP is a baseline that uses the raw Network.Socket interface rather than the Network.Transport abstraction. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Well those results are quite a bit better than mine (from a seemingly identical machine!).
You got 3.35s instead of 7.3 (TCP)
And 8.0s instead of 19 (Network.Transport.TCP)
What gives? I'll check if it's the problem you mentioned with certain port ranges.