crossbar.io problem

#1

Hello

I am testing crossbar.io with Python 2.7.9 in other PC running Windows 7 and
doing this netperf test you have shown here: http://crossbar.io/docs/Stream-Testee/

With netserver.exe on server PC everything goes ok with
TCP_STREAM test netperf -H 10.0.0.10 -t TCP_STREAM -l 60

But when I run test using crossbar.io with this command:
netperf -N -H 10.0.0.10 -t TCP_STREAM -l 60 – -P 9000 my client sends to crossbar.io server ‘TCP Window Full’ and
server sends back ‘TCP Zero Window’ in WireShark after 5 to 6 seconds. If I run only 2 seconds then everything is ok like netperf -N -H 10.0.0.10 -t TCP_STREAM -l 2 – -P 9000

What could be problem here?

I would very much like to use your crossbar.io server but
now I don’t know how to fix this.

With kind regards, Jarkko Peltonen

0 Likes

#2

Hi Jarkko,

Hello

I am testing crossbar.io with Python 2.7.9 in other PC running Windows
7 and doing this netperf test you have shown here:
_http://crossbar.io/docs/Stream-Testee/_

With netserver.exe on server PC everything goes ok with TCP_STREAM test
netperf -H 10.0.0.10 -t TCP_STREAM -l 60

But when I run test using crossbar.io with this command: netperf -N -H
10.0.0.10 -t TCP_STREAM -l 60 -- -P 9000 my client sends to crossbar.io
server ‘TCP Window Full’ and server sends back ‘TCP Zero Window’ in
WireShark after 5 to 6 seconds. If I run only 2 seconds then everything
is ok like netperf -N -H 10.0.0.10 -t TCP_STREAM -l 2 -- -P 9000

What could be problem here?

You OS network settings are not tuned for big, fat pipes. For Linux or FreeBSD, checkout this: http://crossbar.io/docs/Network-Tuning/

I would very much like to use your crossbar.io server but now I don’t
know how to fix this.

This is unlikely related to Crossbar.io, but your specific OS and network settings / tuning.

If you want to replicate the best performance numbers we've published here

http://crossbar.io/docs/Stream-Testee/

then I'd recommend using 2 non-virtualized Linux or FreeBSD boxes connected over 10GbE and using PyPy.

Cheers,
/Tobias

···

Am 29.06.2015 um 15:04 schrieb Jarkko Peltonen:

With kind regards, Jarkko Peltonen

--
You received this message because you are subscribed to the Google
Groups "Crossbar" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to crossbario+...@googlegroups.com
<mailto:crossbario+...@googlegroups.com>.
To post to this group, send email to cross...@googlegroups.com
<mailto:cross...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/crossbario/51ec4950-bf16-4c49-89ea-973c0bcd70dc%40googlegroups.com
<https://groups.google.com/d/msgid/crossbario/51ec4950-bf16-4c49-89ea-973c0bcd70dc%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

0 Likes

#3

Hi

Thanks for reply. I am just worried why netserver.exe works ok for 60 seconds every time in the example and crossbar.io only 6 seconds every time after which I start seeing TCP Zero Window messages in WireShark (https://wiki.wireshark.org/TCP%20ZeroWindow). My connection is through 10/100 switch.

br. Jarkko

maanantai 29. kesäkuuta 2015 16.18.15 UTC+3 Tobias Oberstein kirjoitti:

···

Hi Jarkko,

Am 29.06.2015 um 15:04 schrieb Jarkko Peltonen:

Hello

I am testing crossbar.io with Python 2.7.9 in other PC running Windows

7 and doing this netperf test you have shown here:

_http://crossbar.io/docs/Stream-Testee/_

With netserver.exe on server PC everything goes ok with TCP_STREAM test

netperf -H 10.0.0.10 -t TCP_STREAM -l 60

But when I run test using crossbar.io with this command: netperf -N -H

10.0.0.10 -t TCP_STREAM -l 60 – -P 9000 my client sends to crossbar.io

server ‘TCP Window Full’ and server sends back ‘TCP Zero Window’ in

WireShark after 5 to 6 seconds. If I run only 2 seconds then everything

is ok like netperf -N -H 10.0.0.10 -t TCP_STREAM -l 2 – -P 9000

What could be problem here?

You OS network settings are not tuned for big, fat pipes. For Linux or
FreeBSD, checkout this: http://crossbar.io/docs/Network-Tuning/

I would very much like to use your crossbar.io server but now I don’t

know how to fix this.

This is unlikely related to Crossbar.io, but your specific OS and
network settings / tuning.

If you want to replicate the best performance numbers we’ve published here

http://crossbar.io/docs/Stream-Testee/

then I’d recommend using 2 non-virtualized Linux or FreeBSD boxes
connected over 10GbE and using PyPy.

Cheers,

/Tobias

With kind regards, Jarkko Peltonen

You received this message because you are subscribed to the Google

Groups “Crossbar” group.

To unsubscribe from this group and stop receiving emails from it, send

an email to crossbario+...@googlegroups.com

mailto:crossbario+unsub...@googlegroups.com.

To post to this group, send email to cros...@googlegroups.com

mailto:cross...@googlegroups.com.

To view this discussion on the web visit

https://groups.google.com/d/msgid/crossbario/51ec4950-bf16-4c49-89ea-973c0bcd70dc%40googlegroups.com

<https://groups.google.com/d/msgid/crossbario/51ec4950-bf16-4c49-89ea-973c0bcd70dc%40googlegroups.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.

0 Likes

#4

Hello

I was able to confirm that it wasn’t the server running crossbar.io which sent ‘TCP Zero Window Length’ but it was the client to crossbar.io which ran out of TCP receive buffer for some reason. I still don’t know why it happened.

br. Jarkko

maanantai 29. kesäkuuta 2015 16.18.15 UTC+3 Tobias Oberstein kirjoitti:

···

Hi Jarkko,

Am 29.06.2015 um 15:04 schrieb Jarkko Peltonen:

Hello

I am testing crossbar.io with Python 2.7.9 in other PC running Windows

7 and doing this netperf test you have shown here:

_http://crossbar.io/docs/Stream-Testee/_

With netserver.exe on server PC everything goes ok with TCP_STREAM test

netperf -H 10.0.0.10 -t TCP_STREAM -l 60

But when I run test using crossbar.io with this command: netperf -N -H

10.0.0.10 -t TCP_STREAM -l 60 – -P 9000 my client sends to crossbar.io

server ‘TCP Window Full’ and server sends back ‘TCP Zero Window’ in

WireShark after 5 to 6 seconds. If I run only 2 seconds then everything

is ok like netperf -N -H 10.0.0.10 -t TCP_STREAM -l 2 – -P 9000

What could be problem here?

You OS network settings are not tuned for big, fat pipes. For Linux or
FreeBSD, checkout this: http://crossbar.io/docs/Network-Tuning/

I would very much like to use your crossbar.io server but now I don’t

know how to fix this.

This is unlikely related to Crossbar.io, but your specific OS and
network settings / tuning.

If you want to replicate the best performance numbers we’ve published here

http://crossbar.io/docs/Stream-Testee/

then I’d recommend using 2 non-virtualized Linux or FreeBSD boxes
connected over 10GbE and using PyPy.

Cheers,

/Tobias

With kind regards, Jarkko Peltonen

You received this message because you are subscribed to the Google

Groups “Crossbar” group.

To unsubscribe from this group and stop receiving emails from it, send

an email to crossbario+...@googlegroups.com

mailto:crossbario+unsub...@googlegroups.com.

To post to this group, send email to cros...@googlegroups.com

mailto:cross...@googlegroups.com.

To view this discussion on the web visit

https://groups.google.com/d/msgid/crossbario/51ec4950-bf16-4c49-89ea-973c0bcd70dc%40googlegroups.com

<https://groups.google.com/d/msgid/crossbario/51ec4950-bf16-4c49-89ea-973c0bcd70dc%40googlegroups.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.

0 Likes