Tourney Server Speeds

[kyle]

I discovered speedtest-cli And curious what our competition servers might have for speeds.

It is pretty simple to use

Code: Select all

wget -O speedtest-cli https://raw.github.com/sivel/speedtest-cli/master/speedtest_cli.py
python speedtest-cli 

you can add options to that like --share (to get the image to share withe others) and --server to test it with another server 3969 is in Germany and 3595 is in Atlanta, GA, USA

CT USA (default test server)

CT USA (server 3969, Germany)


CT LIV (default test server)

CT LIV (server 3595 Atlanta, GA, USA)


So what are some of the others that we use?

[Light]

I think a ping test would be more appropriate since it uses so little bandwidth. See how stable the connections are, rather than their top speeds. It usually doesn't say how slowly it reaches that speed either, since some are much slower than others.

Other than that, hardware would be the other thing to look into, but I don't know if there's a universal test for that as easily available as ping/bw tests.

Mine is like 70-90 Mb/s down and 4.5 Mb/s up. Home connection, if you need an explanation for the up speed. The Tron servers don't come close to using it anyways.

I'll do a test when I'm done running my script and servers are empty. It's been running since like noon and using so much of my CPU. Future plan .. don't wait till something explodes to do it right. lol Bleh, off topic .. shutting up now.

[sinewav]

Here is a crazy idea: is there any network information in debug recording we can use to asses a server's performance? It would be neat to batch process the post Ladle aarec's and use some of that data to rank server quality.

[kyle]

pingtest would be better, since jitter is a better measure of the connection quality, But i don't see any command line versions of that

[Light]

pingtest would be better, since jitter is a better measure of the connection quality, But i don't see any command line versions of that

Yeah, that's where I got lucky. I have like a 2ms jitter on a home connection with around 30ish ping. It seems to work out for me. Now if only I wasn't running it on a shitty server that I rescued from being tossed to the garbage.

I'll see if I can find a ping test.

[Light]

Iperf with -u (UDP) parameter seems to show jitter. I haven't really looked into it a whole lot yet, but may be worth a try. I probably have to wait until tomorrow to have any realistic tests, so if you don't want to, I'll check into it then.

[delinquent]

Ashes - Bristol

Up speed is refusing to co-operate despite numerous kicks, verbal abuse and other unsightly actions. It is about 80Mbps from previous tests.

ping.png

(7.72 KiB) Not downloaded yet

Better ping/jitter test:

[Light]

Better ping/jitter test:

Yeah, but we were looking for a command line ping test for linux servers. Of course, I could use another computer on the network.

[delinquent]

I was just posting my own results tbh.

Iperf seems to require a host, although the windows build does not.

I think smokeping might be your answer here. You gotta disable SElinux though
config file can usually be found here:

Code: Select all

sudo vi /etc/selinux/config

then it's as simple as

SELINUX=disable

Then via aptitude for debian/ubuntu

Code: Select all

sudo aptitude update
sudo aptitude install smokeping curl libauthen-radius-perl libnet-ldap-perl libnet-dns-perl libio-socket-ssl-perl libnet-telnet-perl libsocket6-perl libio-socket-inet6-perl apache2 sendmail

Fedora is just

Code: Select all

sudo yum install smokeping

config is something like the following:

Code: Select all

sudo vi /etc/smokeping/config.d/General

and use it like so:

cgiurl = http://<ipaddressofhost>/cgi-bin/smokeping.cgi

I think it uses fping by default, tcpping is allowed too

Code: Select all

sudo vi /etc/smokeping/config.d/Probes

then this is what is in my probe config:

+ FPing

binary = /usr/bin/fping
offset = 50%
step = 60
timeout = 10
pings = 5

+ TCPPing

binary = /usr/bin/tcpping
forks = 5
offset = 50%
step = 60
timeout = 10
pings = 5

Fork is akin to the number of processes used, offset is a variation of concurrent probes relative to start time at a given timepoint. Step is the duration of probing in seconds, timeout is obvious and pings is the total during an interval.

You can set more than one target too, using

Code: Select all

sudo vi /etc/smokeping/config.d/Targets

probe = FPing
menu = Latency
title = Latency Measurement
remark = SmokePing Latency Test.

+ Internal_Host
menu = Internal_Hosts
title = Cloud Latency Measurements

++ Home
title = Home
host = 192.168.1.6

++ Google_UK
title = Google UK
host = 74.125.24.94

++ CT
title = ptacrazytronners
host = 78.46.226.236

You can add "probe" too, specifying the protocol to use.

Also, whenever you make changes, smokeping has to be restarted. It runs as a service on Fedora, AFAIK.

That do?

**Edit: Forgot something: program doesn't go in /bin, the path is /etc/init.d/smokeping if you need to restart it