valitydev/yandex-tank
14
0
Fork 0
mirror of https://github.com/valitydev/yandex-tank.git synced 2024-11-06 10:25:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

change example IP addresses in README according to rfc5737

Browse Source
This commit is contained in:
Alexey Lavrenuke (load testing) 2013-07-18 14:02:36 +04:00
parent 050f5877cd
commit bf96914324
2 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
README.md
View File

@ -37,7 +37,7 @@ Create a file on a server with Yandex.Tank:
**load.conf** **load.conf**
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=line(1, 100, 10m) #load scheme rps_schedule=line(1, 100, 10m) #load scheme
``` ```
Yandex.Tank have 3 primitives for describing load scheme: Yandex.Tank have 3 primitives for describing load scheme:
@ -58,7 +58,7 @@ Time duration could be defined in seconds, minutes (m) and hours (h). For exampl
For a test with constant load at 10rps for 10 minutes, load.conf should have next lines: For a test with constant load at 10rps for 10 minutes, load.conf should have next lines:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
``` ```
Voilà, Yandex.Tank setup is done. Voilà, Yandex.Tank setup is done.
@ -72,7 +72,7 @@ URIs listed in load.conf or in a separate file.
Update configuration file with HTTP headers and URIs: Update configuration file with HTTP headers and URIs:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme# Headers and URIs for GET requests rps_schedule=const(10, 10m) #load scheme# Headers and URIs for GET requests
header_http = 1.1 header_http = 1.1
headers = [Host: www.target.example.com] headers = [Host: www.target.example.com]
@ -228,7 +228,7 @@ To activate SSL add 'ssl = 1' to load.conf. Don't forget to change port number t
Now, our basic config looks like that: Now, our basic config looks like that:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const (10,10m) #Load scheme rps_schedule=const (10,10m) #Load scheme
ssl=1 ssl=1
``` ```
@ -248,7 +248,7 @@ Example:
So, if we want to stop test when all answers in 1 second period are 5xx plus some network and timing factors - add autostop line to load.conf: So, if we want to stop test when all answers in 1 second period are 5xx plus some network and timing factors - add autostop line to load.conf:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
[autostop] [autostop]
autostop=time(1,10) autostop=time(1,10)
@ -286,7 +286,7 @@ Content-Type: application/javascript;charset=UTF-8
For ```load.conf``` like this: For ```load.conf``` like this:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
writelog=1 writelog=1
[autostop] [autostop]
@ -326,7 +326,7 @@ use your favorite stats packet, R, for example.
You can set custom timings in ```load.conf``` with ```time_periods``` parameter like this: You can set custom timings in ```load.conf``` with ```time_periods``` parameter like this:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
[aggregator] [aggregator]
time_periods = 10 45 50 100 150 300 500 1s 1500 2s 3s 10s # the last value - 10s is considered as connect timeout. time_periods = 10 45 50 100 150 300 500 1s 1500 2s 3s 10s # the last value - 10s is considered as connect timeout.
@ -337,7 +337,7 @@ time_periods = 10 45 50 100 150 300 500 1s 1500 2s 3s 10s # the last value - 10s
Test with 10 threads: Test with 10 threads:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
instances=10 instances=10
``` ```
@ -347,7 +347,7 @@ instances=10
load.conf example: load.conf example:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
instances_schedule = line(1,10,10m) instances_schedule = line(1,10,10m)
#load = const (10,10m) #Load scheme is excluded from this load.conf as we used instances_schedule parameter #load = const (10,10m) #Load scheme is excluded from this load.conf as we used instances_schedule parameter
``` ```
@ -359,7 +359,7 @@ To do that add ```tank_type = 2``` to ```load.conf```.
load.conf example: load.conf example:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
instances=10 instances=10
tank_type=2 tank_type=2
@ -369,10 +369,10 @@ If server with Yandex.Tank have several IPs, they may be used to avoid outcome p
Load.conf: Load.conf:
``` ```
[phantom] [phantom]
address=23.23.23.23:80 #Target's address and port . address=203.0.113.1:80 #Target's address and port .
rps_schedule=const(10, 10m) #load scheme rps_schedule=const(10, 10m) #load scheme
instances=10 instances=10
gatling_ip = 23.23.23.24 23.23.23.26 gatling_ip = 203.0.113.2 203.0.113.3
``` ```
**run yandex-tank with -g key** **run yandex-tank with -g key**
@ -600,7 +600,7 @@ Yandex.Tank sources ((https://github.com/yandex-load/yandex-tank here)).
### load.conf.example ### load.conf.example
``` ```
# Yandex.Tank config file # Yandex.Tank config file
address=23.23.23.23:443 #Target's address and port address=203.0.113.1:443 #Target's address and port
load = const (10,10m) #Load scheme load = const (10,10m) #Load scheme
# Headers and URIs for GET requests # Headers and URIs for GET requests
header_http = 1.1 header_http = 1.1
@ -624,9 +624,9 @@ Before test execution, please, check service availability. If service is running
```telnet x.x.x.x zz``` ```telnet x.x.x.x zz```
If everything OK, you'll see: If everything OK, you'll see:
``` ```
$ telnet 23.23.23.23 80 $ telnet 203.0.113.1 80
Trying 23.23.23.23... Trying 203.0.113.1...
Connected to 23.23.23.23. Connected to 203.0.113.1.
Escape character is '^]'. Escape character is '^]'.
``` ```
Otherwise if port is unreacheable: Otherwise if port is unreacheable:
@ -640,24 +640,24 @@ telnet: Unable to connect to remote host: Connection timed out
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: 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 $ tracepath 203.0.113.2
1: tank.example.com (23.23.23.23) 0.084ms pmtu 1450 1: tank.example.com (203.0.113.1) 0.084ms pmtu 1450
1: target.load.example.com (23.23.23.24) 20.919ms reached 1: target.load.example.com (203.0.113.2) 20.919ms reached
1: target.example.com (23.23.23.24) 0.128ms reached 1: target.example.com (203.0.113.2) 0.128ms reached
Resume: pmtu 1450 hops 1 back 64 Resume: pmtu 1450 hops 1 back 64
``` ```
Hops count = 1 means that tank and target are in closest location. Hops count = 1 means that tank and target are in closest location.
``` ```
$ tracepath 24.24.24.24 $ tracepath 203.0.113.10
1: 1.example.com (124.24.24.24) 0.084ms pmtu 1450 1: 1.example.com (203.0.113.21) 0.084ms pmtu 1450
1: 2.example.com (24.124.24.24) 0.276ms 1: 2.example.com (203.0.113.22) 0.276ms
1: 3.example.com (24.24.124.24) 0.411ms 1: 3.example.com (203.0.113.23) 0.411ms
2: 4.example.com (24.24.24.124) 0.514ms 2: 4.example.com (203.0.113.24) 0.514ms
3: 5.example.com (241.24.24.24) 10.690ms 3: 5.example.com (203.0.113.25) 10.690ms
4: 6.example.com (24.241.24.24) 0.831ms asymm 3 4: 6.example.com (203.0.113.26) 0.831ms asymm 3
5: 7.example.com (24.24.241.24) 0.512ms 5: 7.example.com (203.0.113.27) 0.512ms
6: 8.example.com (24.24.24.241) 0.525ms asymm 5 6: 8.example.com (203.0.113.28) 0.525ms asymm 5
7: no reply 7: no reply
``` ```
In this example you'd better find another closer located tank. In this example you'd better find another closer located tank.

2
Tank/stepper/info.py
View File

@ -112,4 +112,4 @@ class StepperStatus(object):
"Information for %s is not published yet." % key) "Information for %s is not published yet." % key)
return StepperInfo(**self.info) return StepperInfo(**self.info)
status = StepperStatus() status = StepperStatus()