-
Notifications
You must be signed in to change notification settings - Fork 279
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
Windows | Expected Throughput #643
Comments
Did you increase the send/recv socket buffer sizes? If not, does doing so improve things? |
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. 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... |
How much?
You can capture the traffic using wireshark and take a look or provide the capture file...
If you are not using loss and delay. What is limiting the transmission? The CPU load?
I think so... But I have no experience with Windows... |
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.
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.
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? |
I am trying to evaluate if this library can be used for a Project.
To get the best throughput results i've tried different ways to implement the Lib, using the no threaded init, normal init etc.
Now with the normal threaded implementation, trying a few different settings this is my current throughput.
I've checked and the core running at max load, analyzing the cpu time my code also doesn't take away too much time.
So - question. Is this kind of expected on Windows or are there maybe some default settings which are known to increase performance?
Results:
OS: Windows 10
CPU : Intel i7-10700K CPU @ 3.8GHz
Using default sctp_init without callback api
Sender is in virtual machine. Network is over HyperV V-Switch
Using "clumsy" as network fuzzer
Current commit : f7368e6
Application was build without optimization
When simulating a not perfect network i get the following result
(Take this with a grain of salt - the fuzzing tool seems to have some problems)
10ms60-100msThe text was updated successfully, but these errors were encountered: