mirror of
https://github.com/valitydev/yandex-tank.git
synced 2024-11-06 02:15:22 +00:00
Update README.md
This commit is contained in:
Oles Pisarenko
parent
00368d269b
commit
e6c4ad14e3
150
README.md
150
README.md
@ -24,91 +24,9 @@ Then update package list and install ```yandex-load-tank-base``` package:
|
||||
```sudo apt-get update && sudo apt-get install yandex-load-tank-base```
|
||||
|
||||
For mild load tests (less then 1000rps) an average laptop with 32/64bit Ubuntu (Lucid/Precise) would be sufficient.
|
||||
|
||||
Create load.conf file in local directory:
|
||||
```
|
||||
[phantom]
|
||||
address = 127.0.0.1:80
|
||||
rps_schedule = const(1,1m)
|
||||
uris = /
|
||||
```
|
||||
...and start tank from console:
|
||||
```
|
||||
$ yandex-tank
|
||||
```
|
||||
|
||||
Perfomance testing utility starts after several seconds. Enjoy!
|
||||
|
||||
|
||||
The tank could be easily used in virtual machine if queries aren't too heavy and load isn't too big.
|
||||
Otherwise it is recommended to request a physical server or a more capable virtual machine from your admin.
|
||||
|
||||
### Firewall
|
||||
|
||||
Before test execution, please, check service availability. If service is running on server with IP x.x.x.x and listening for TCP port zz, try to connect to it with ```telnet``` like this:
|
||||
```telnet x.x.x.x zz```
|
||||
If everything OK, you'll see:
|
||||
```
|
||||
$ telnet 23.23.23.23 80
|
||||
Trying 23.23.23.23...
|
||||
Connected to 23.23.23.23.
|
||||
Escape character is '^]'.
|
||||
```
|
||||
Otherwise if port is unreacheable:
|
||||
```
|
||||
$ telnet 8.8.8.8 80
|
||||
Trying 8.8.8.8...
|
||||
telnet: Unable to connect to remote host: Connection timed out
|
||||
```
|
||||
(it's just an example, programs like ```nc/nmap/wget/curl``` could be used as well, but not ping!)
|
||||
### Routing
|
||||
OK, service is reachable, next thing you should know is how far Yandex.Tank is located from the service you'd like to test. Heavy load can make switch to be unresponsible or to reboot, or at least it may lead to network losses, so the test results would be distorted. Be careful. Path estimation could be done by execution of ```tracepath``` command or it analogs (```tracert/traceroute```) on Yandex.Tank machine:
|
||||
|
||||
```
|
||||
$ tracepath 23.23.23.24
|
||||
1: tank.example.com (23.23.23.23) 0.084ms pmtu 1450
|
||||
1: target.load.example.com (23.23.23.24) 20.919ms reached
|
||||
1: target.example.com (23.23.23.24) 0.128ms reached
|
||||
Resume: pmtu 1450 hops 1 back 64
|
||||
```
|
||||
Hops count = 1 means that tank and target are in closest location.
|
||||
|
||||
```
|
||||
$ tracepath 24.24.24.24
|
||||
1: 1.example.com (124.24.24.24) 0.084ms pmtu 1450
|
||||
1: 2.example.com (24.124.24.24) 0.276ms
|
||||
1: 3.example.com (24.24.124.24) 0.411ms
|
||||
2: 4.example.com (24.24.24.124) 0.514ms
|
||||
3: 5.example.com (241.24.24.24) 10.690ms
|
||||
4: 6.example.com (24.241.24.24) 0.831ms asymm 3
|
||||
5: 7.example.com (24.24.241.24) 0.512ms
|
||||
6: 8.example.com (24.24.24.241) 0.525ms asymm 5
|
||||
7: no reply
|
||||
```
|
||||
In this example you'd better find another closer located tank.
|
||||
|
||||
### Tuning
|
||||
To achieve the top most performance you should tune the source server system limits:
|
||||
```
|
||||
ulimit -n 30000
|
||||
|
||||
net.ipv4.tcp_max_tw_buckets = 65536
|
||||
net.ipv4.tcp_tw_recycle = 1
|
||||
net.ipv4.tcp_tw_reuse = 0
|
||||
net.ipv4.tcp_max_syn_backlog = 131072
|
||||
net.ipv4.tcp_syn_retries = 3
|
||||
net.ipv4.tcp_synack_retries = 3
|
||||
net.ipv4.tcp_retries1 = 3
|
||||
net.ipv4.tcp_retries2 = 8
|
||||
net.ipv4.tcp_rmem = 16384 174760 349520
|
||||
net.ipv4.tcp_wmem = 16384 131072 262144
|
||||
net.ipv4.tcp_mem = 262144 524288 1048576
|
||||
net.ipv4.tcp_max_orphans = 65536
|
||||
net.ipv4.tcp_fin_timeout = 10
|
||||
net.ipv4.tcp_low_latency = 1
|
||||
net.ipv4.tcp_syncookies = 0
|
||||
```
|
||||
|
||||
## Usage
|
||||
So, you've installed Yandex.Tank to a proper server, close to target, access is permitted and server is tuned.
|
||||
How to make a test?
|
||||
@ -698,6 +616,74 @@ uri = /
|
||||
#gatling_ip = 141.8.153.82 141.8.153.81
|
||||
|
||||
```
|
||||
## Load server Configuration and Tunning
|
||||
### Firewall
|
||||
|
||||
Before test execution, please, check service availability. If service is running on server with IP x.x.x.x and listening for TCP port zz, try to connect to it with ```telnet``` like this:
|
||||
```telnet x.x.x.x zz```
|
||||
If everything OK, you'll see:
|
||||
```
|
||||
$ telnet 23.23.23.23 80
|
||||
Trying 23.23.23.23...
|
||||
Connected to 23.23.23.23.
|
||||
Escape character is '^]'.
|
||||
```
|
||||
Otherwise if port is unreacheable:
|
||||
```
|
||||
$ telnet 8.8.8.8 80
|
||||
Trying 8.8.8.8...
|
||||
telnet: Unable to connect to remote host: Connection timed out
|
||||
```
|
||||
(it's just an example, programs like ```nc/nmap/wget/curl``` could be used as well, but not ping!)
|
||||
### Routing
|
||||
OK, service is reachable, next thing you should know is how far Yandex.Tank is located from the service you'd like to test. Heavy load can make switch to be unresponsible or to reboot, or at least it may lead to network losses, so the test results would be distorted. Be careful. Path estimation could be done by execution of ```tracepath``` command or it analogs (```tracert/traceroute```) on Yandex.Tank machine:
|
||||
|
||||
```
|
||||
$ tracepath 23.23.23.24
|
||||
1: tank.example.com (23.23.23.23) 0.084ms pmtu 1450
|
||||
1: target.load.example.com (23.23.23.24) 20.919ms reached
|
||||
1: target.example.com (23.23.23.24) 0.128ms reached
|
||||
Resume: pmtu 1450 hops 1 back 64
|
||||
```
|
||||
Hops count = 1 means that tank and target are in closest location.
|
||||
|
||||
```
|
||||
$ tracepath 24.24.24.24
|
||||
1: 1.example.com (124.24.24.24) 0.084ms pmtu 1450
|
||||
1: 2.example.com (24.124.24.24) 0.276ms
|
||||
1: 3.example.com (24.24.124.24) 0.411ms
|
||||
2: 4.example.com (24.24.24.124) 0.514ms
|
||||
3: 5.example.com (241.24.24.24) 10.690ms
|
||||
4: 6.example.com (24.241.24.24) 0.831ms asymm 3
|
||||
5: 7.example.com (24.24.241.24) 0.512ms
|
||||
6: 8.example.com (24.24.24.241) 0.525ms asymm 5
|
||||
7: no reply
|
||||
```
|
||||
In this example you'd better find another closer located tank.
|
||||
|
||||
### Tuning
|
||||
To achieve the top most performance you should tune the source server system limits:
|
||||
```
|
||||
ulimit -n 30000
|
||||
|
||||
net.ipv4.tcp_max_tw_buckets = 65536
|
||||
net.ipv4.tcp_tw_recycle = 1
|
||||
net.ipv4.tcp_tw_reuse = 0
|
||||
net.ipv4.tcp_max_syn_backlog = 131072
|
||||
net.ipv4.tcp_syn_retries = 3
|
||||
net.ipv4.tcp_synack_retries = 3
|
||||
net.ipv4.tcp_retries1 = 3
|
||||
net.ipv4.tcp_retries2 = 8
|
||||
net.ipv4.tcp_rmem = 16384 174760 349520
|
||||
net.ipv4.tcp_wmem = 16384 131072 262144
|
||||
net.ipv4.tcp_mem = 262144 524288 1048576
|
||||
net.ipv4.tcp_max_orphans = 65536
|
||||
net.ipv4.tcp_fin_timeout = 10
|
||||
net.ipv4.tcp_low_latency = 1
|
||||
net.ipv4.tcp_syncookies = 0
|
||||
```
|
||||
|
||||
|
||||
|
||||
## See also
|
||||
Evgeniy Mamchits' [phantom](https://github.com/mamchits/phantom) - Phantom scalable IO Engine
|
||||
|
||||
Loading…
Reference in New Issue
Block a user