Confirmed users
487
edits
Services/TrackingProtection/Shavar Server - Testing: Difference between revisions
Jump to navigation
Jump to search
m
Services/TrackingProtection/Shavar Server - Testing (view source)
Revision as of 21:04, 17 December 2015
, 17 December 2015formatting
Rpappalardo (talk | contribs) (Updated for loadtesting strategy notes) |
Rpappalardo (talk | contribs) m (formatting) |
||
| Line 288: | Line 288: | ||
* of -t [AWS instance size] | * of -t [AWS instance size] | ||
* using -k <SSH keypair (pem file) name> | * using -k <SSH keypair (pem file) name> | ||
<code> | <code> | ||
| Line 293: | Line 294: | ||
$ ./bees up -s 20 -k loads -t t2.medium | $ ./bees up -s 20 -k loads -t t2.medium | ||
</code> | </code> | ||
once bees are running, the following test will create: | once bees are running, the following test will create: | ||
| Line 298: | Line 300: | ||
* for a test of duration -w [seconds] | * for a test of duration -w [seconds] | ||
* using siege engine --use-siege | * using siege engine --use-siege | ||
<code> | <code> | ||
./bees attack --use-siege -c 20 -w 300s -u 'http://<shavar-stage-url-here>/downloads POST mozpub-track-digest256;a:1424217132' | ./bees attack --use-siege -c 20 -w 300s -u 'http://<shavar-stage-url-here>/downloads POST mozpub-track-digest256;a:1424217132' | ||
</code> | </code> | ||
* Increase -c and -r from 10 -> 100 -> 500 -> 1000 | * Increase -c and -r from 10 -> 100 -> 500 -> 1000 | ||
| Line 309: | Line 313: | ||
** note: that is considered 'safe' to account for any spikes/fluctuations that may increase things to 100% usage | ** note: that is considered 'safe' to account for any spikes/fluctuations that may increase things to 100% usage | ||
** Whatever number of requests per second (RPS) being sent at 60% threshold = amount of load the stack can safely handle | ** Whatever number of requests per second (RPS) being sent at 60% threshold = amount of load the stack can safely handle | ||
Example test run: | Example test run: | ||