uniquoo
uniquoo
Comments
-
OVH, KS-LE [root@* ~]# curl -sL yabs.sh | bash# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## Yet-Another-Bench-Script ## v2022-08-20 ## https://github.com/masonr/yet-another-bench-script ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #Mo 22. Aug 09:43:20 CEST 2022Basic System…
-
OVH - Kimsufi - KS-01 (with 2TB instead 1TB) [root@* ~]# curl -sL yabs.sh | bash# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## Yet-Another-Bench-Script ## v2022-08-20 ## https://github.com/masonr/yet-another-bench-script ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #So 21. Aug 22:52:50 CEST 2022Basic…
-
To be honest with you, i've yet to find the bottleneck which causes the problems described. I've tested locally with multiple streams (using multiple ports and so multiple iPerf3-daemons on multiple cores) and was able to achieve 100 Gbit consistently. Right now i'm debugging with our backbone department to rule out…
-
Yep. According to ESNETs advice for 40/100g interfaces
-
Update: It looks like everyone is testing against one single Port. Because iPerf3 is single threaded i'd like to ask you to test the throughput the following way: iperf3 -c speedtest.wtnet.de -s t1 -p 5301 -P 2 -4 & iperf3 -c speedtest.wtnet.de -s t2 -p 5302 -P 2 -4 & iperf3 -c speedtest.wtnet.de -s t3 -p 5303 -P 2 -4 &…
-
I'm currently checking into tunables and routing issues with out backbone. Please give me some time to so i can hopefully fix this. Within Germany I've seen tests up to 19,8 Gbit so far. Yet not close enough to 40G. Sorry. Will update this post once i can update you with hopefully good news on this.
-
iPerf intances are restarted every night. Do you still have problems reaching other ports ?
-
Same. Left LET after 11 years. Businessmodel my ass.
-
Thanks for letting me know. I'm in the process of generating these files now. Update: Should be fixed now.