-
-
Notifications
You must be signed in to change notification settings - Fork 605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
netperf tcp_cc results are unstable #383
Comments
|
asias
changed the title
netperf tcp_cc result is not unstable
netperf tcp_cc results are unstable
Jul 14, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
client side (linux): netperf connect() recv()
server side (osv): netserver listen() accept() close()
client side creates a connection, server accepts the connection and
closes it immediately, client side will return from recv(). This
completes a single transaction. client will repeat above. The
benchmark score is N Transaction/second.
Since OSv closes the socket first, OSv will have a lot socket in
TIME_WAIT state. This explains why increasing the TCBHASHSIZE would
decrease the cpu usage.
Centos has a very stable 12K Trans/s results, while OSv has a very
unstable results: from <1k, 1K, 3K to 12K.
I used strace to see time spend on connect() and recv() syscall in
client side. They usually takes ~100us to complete each.
When OSv has bad results, some of the recv() take up to ~200000us.
This is the show stopper for performance. So probably, OSv has
slowness doing the close() on the socket in some cases
The text was updated successfully, but these errors were encountered: