sctplab/usrsctp

benchmarking

asterwyx opened this issue · 6 comments

Hi owners, this may be a question. I wonder if there is a professional tool to measure the throughput of usrsctp. I mean, it's better not to write any code on my own. I wonder how you do your benchmark on usrsctp, and what's the common performance. Can you give me a reference? Thanks!

I'm doing this normally only for the kernel stack using tsctp or uperf. We do have tsctp ported to the userland stack. So you could try that...

I'm not sure about tsctp you've mentioned. I've searched just now in google. Is it an open-source project by nplab in Github? What about the tsctp ported to userland stack. Is it referring to the file "tsctp.c" under programs folder of usrsctp?

I'm not sure about tsctp you've mentioned. I've searched just now in google. Is it an open-source project by nplab in Github? What about the tsctp ported to userland stack. Is it referring to the file "tsctp.c" under

Correct. I wrote it years ago the be able to do testing. It was named after ttcp, just for SCTP. That is the reason for the name. It was mainly used to test throughput in dependency of streams, message size, and so on.

programs folder of usrsctp?

Yepp. That is the port to usrsctp I was referring to.

I'm not sure about tsctp you've mentioned. I've searched just now in google. Is it an open-source project by nplab in Github? What about the tsctp ported to userland stack. Is it referring to the file "tsctp.c" under

Correct. I wrote it years ago the be able to do testing. It was named after ttcp, just for SCTP. That is the reason for the name. It was mainly used to test throughput in dependency of streams, message size, and so on.

programs folder of usrsctp?

Yepp. That is the port to usrsctp I was referring to.

I haven't found any user guide about these two programs. Is there any simple example? I just want to measure throughput between two nodes and will not use UDP encapsulation.

You can start the server by just running tsctp. The server is just receiving messages. The client can be started with tsctp remote-addres. It will send 1024 messages of 1024 byte. You can use -n number to change the number of messages, -l length to change the size of the messages. Instead of sending a specific number of messages, you can use -T time to specify the number seconds to send messages. You can use tsctp -h to get a list of supported parameters.

You can start the server by just running tsctp. The server is just receiving messages. The client can be started with tsctp remote-addres. It will send 1024 messages of 1024 byte. You can use -n number to change the number of messages, -l length to change the size of the messages. Instead of sending a specific number of messages, you can use -T time to specify the number seconds to send messages. You can use tsctp -h to get a list of supported parameters.

Thanks!