Windows | Expected Throughput about usrsctp HOT 4 OPEN

Did you increase the send/recv socket buffer sizes? If not, does doing so improve things?

from usrsctp.

I had them increased, Yes.

I however I only build the application in Debug mode. Building it in release with compiler optimization the throughput is doubled... So, that's something I should have thought about.

Also, the Lag test is invalid, the tool I'm using is creating much higher Latency then it shows.
I assume the drop test is also incorrect.

However now I get very weird results for the UnorderedTTLLossy packet (SCTP_PR_SCTP_TTL+ 50 ms), haven't really changed anything there thought. Also I noticed they generate quite a lot of backtraffic - sending 80mbit & receiving 40-80mbit?

New values

I still think I'm doing something wrong...
Other Question though - tscp/tscp_upcall should work like:
server : tsctp_upcall.exe
client : tsctp_upcall.exe <server-ip>
Correct?

from usrsctp.

I had them increased, Yes.

How much?

I however I only build the application in Debug mode. Building it in release with compiler optimization the throughput is doubled... So, that's something I should have thought about.
Yes adding debug support requires some cycles...

Also, the Lag test is invalid, the tool I'm using is creating much higher Latency then it shows. I assume the drop test is also incorrect.

However now I get very weird results for the UnorderedTTLLossy packet (SCTP_PR_SCTP_TTL+ 50 ms), haven't really changed anything there thought. Also I noticed they generate quite a lot of backtraffic - sending 80mbit & receiving 40-80mbit?

You can capture the traffic using wireshark and take a look or provide the capture file...

New values

Type PcktSize Reliability mbyte/s pkt/s  
OrderedLosless 64000 1 95.04 1485  
OrderedLosless 32000 1 87.52 2735  
OrderedLosless 16000 1 89.98 5624  
OrderedLosless 8000 1 85.76 10720  
OrderedLosless 4000 1 78.86 19716  
OrderedLosless 500 1 31.75 63492  
UnorderedRTXLoss 16000 0.99 80.05 5003  
UnorderedTTLLoss 16000 0.75 5.68 355  
           
OrderedLosless 16000 1 89.98 5624  
OrderedLosless 16000 1 3.15 197 10-40ms latency
OrderedLosless 16000 1 14.80 925 2.5% drop chance in/out
OrderedLosless 16000 1 33.71 2107 50% out of order
OrderedLosless 16000 1 21.47 1342 2.5% tamper chance in/out
           
UnorderedRTXLoss 16000 0.74 14.09 881 2.5% drop chance in/out
UnorderedTTLLoss 16000 0.74 3.03 190 2.5% drop chance in/out

If you are not using loss and delay. What is limiting the transmission? The CPU load?

I still think I'm doing something wrong... Other Question though - tscp/tscp_upcall should work like: server : tsctp_upcall.exe client : tsctp_upcall.exe <server-ip> Correct?

I think so... But I have no experience with Windows...

from usrsctp.

How much?

Way too huge honestly, 256mb for both. Wanted to see if it makes a noticeable difference since a lot of changes I tried just resulted in the same result.

You can capture the traffic using wireshark and take a look or provide the capture file...

Will take a look tomorrow. I was just suprized to see that and thought maybe that's something which is to be expected. I personally don't really need the TTL reliability mode anyways.

If you are not using loss and delay. What is limiting the transmission? The CPU load?

You mean when using OrderedLossless? Yes It's the CPU on the sending side. With a older version of the testcode the Server could handle ~ 1.6x the Load one sender could send. Might be different now ofc.

Question - could you give me a very rought hint on how much throughput you would expect?

from usrsctp.