Ab - Revision history

Onnowpurbo: /* Normal Benchmark */

2018-12-12T03:24:54Z

Normal Benchmark

← Older revision		Revision as of 03:24, 12 December 2018
Line 12:		Line 12:

	ab -kc 20 -t 60 http://192.168.0.100/index.html		ab -kc 20 -t 60 http://192.168.0.100/index.html
			ab -kc 20 -t 60 http://192.168.0.3:8080/wikipedia_id_all_novid_2018-07/

	Dimana		Dimana
Line 74:		Line 75:
	99% 53		99% 53
	100% 109 (longest request)		100% 109 (longest request)


	==Flood Test==		==Flood Test==

Onnowpurbo: /* Instalasi ab */

2018-12-07T10:11:56Z

Instalasi ab

← Older revision		Revision as of 10:11, 7 December 2018
Line 6:		Line 6:
	==Instalasi ab==		==Instalasi ab==

	apt~~-get~~ install apache2-utils tcpdump		apt update
			apt install apache2-utils tcpdump

	==Normal Benchmark==		==Normal Benchmark==

Onnowpurbo: /* Pranala Menarik */

2018-12-07T10:06:57Z

Pranala Menarik

← Older revision		Revision as of 10:06, 7 December 2018
Line 205:		Line 205:
	==Pranala Menarik==		==Pranala Menarik==

			* [[ab: 7 tip untuk heavy load ab benchmark]]
	* [[Network Benchmarking]]		* [[Network Benchmarking]]

Onnowpurbo: /* Referensi */

2018-12-06T04:40:11Z

Referensi

← Older revision		Revision as of 04:40, 6 December 2018
Line 201:		Line 201:

	* https://wiki.appnexus.com/display/documentation/How+to+Apache+Stress+Test+With+ab+Tool		* https://wiki.appnexus.com/display/documentation/How+to+Apache+Stress+Test+With+ab+Tool


			==Pranala Menarik==

			* [[Network Benchmarking]]

Onnowpurbo: /* Flood Test */

2018-11-19T10:24:51Z

Flood Test

← Older revision		Revision as of 10:24, 19 November 2018
Line 82:		Line 82:
	ab -n 10000 -c 400 http://192.168.0.100/index.html		ab -n 10000 -c 400 http://192.168.0.100/index.html
	ab -n 1000 -c 10 -g test_data_1.txt http://www.your-domain.com/index.html		ab -n 1000 -c 10 -g test_data_1.txt http://www.your-domain.com/index.html
	ab -n 10000 -c 400 -g test_data_1.txt http://192.168.0.238/DVWA-1.9/login.php		ab -n 10000 -c 400 -A admin:password -g test_data_1.txt http://192.168.0.238/DVWA-1.9/login.php

Onnowpurbo: /* Flood Test */

2018-11-19T10:21:39Z

Flood Test

← Older revision		Revision as of 10:21, 19 November 2018
Line 82:		Line 82:
	ab -n 10000 -c 400 http://192.168.0.100/index.html		ab -n 10000 -c 400 http://192.168.0.100/index.html
	ab -n 1000 -c 10 -g test_data_1.txt http://www.your-domain.com/index.html		ab -n 1000 -c 10 -g test_data_1.txt http://www.your-domain.com/index.html
			ab -n 10000 -c 400 -g test_data_1.txt http://192.168.0.238/DVWA-1.9/login.php


	Hasilnya:		Hasilnya:

Onnowpurbo at 09:49, 19 November 2018

2018-11-19T09:49:53Z

@@ Line 81: / Line 81: @@
   ab -n 10000 -c 400 http://192.168.0.100/index.html
 Hasilnya:
@@ Line 164: / Line 165: @@
 dimana 192.168.0.100 adalah IP server.

Onnowpurbo at 10:51, 9 June 2015

2015-06-09T10:51:59Z

Show changes

Onnowpurbo: New page: Performance Testing your Web Server To benchmark the performance of your web server applications we recommend the Apache "ab" tool. The ab tool will show how many requests per second you...

2015-06-08T21:52:50Z

New page: Performance Testing your Web Server To benchmark the performance of your web server applications we recommend the Apache "ab" tool. The ab tool will show how many requests per second you...

New page

Performance Testing your Web Server

To benchmark the performance of your web server applications we recommend the Apache "ab" tool. The ab tool will show how many requests per second your Apache installation is capable of serving. The ab tool is a part of the Apache httpd package in CentOS and Red Hat distributions and the "apache2-utils" package in Debian.

Below is the basic ab command and its output. The -c parameter specifies the number of connections; the -k stands for HTTP Keep-Alive; and the -t parameter sets the time in seconds for which each connection is alive. The application is then hammered through those connections.

# ab -kc 20 -t 60 http://8.19.73.87/index.html

Benchmarking 8.19.73.87 (be patient)
Finished 130 requests

Server Software: Apache/2.2.3
Server Hostname: 8.19.73.87
Server Port: 80

Document Path: /index.html
Document Length: 283 bytes

Concurrency Level: 20
Time taken for tests: 62.269650 seconds
Complete requests: 130
Failed requests: 0
Write errors: 0
Non-2xx responses: 130
Keep-Alive requests: 0
Total transferred: 60060 bytes
HTML transferred: 36790 bytes
Requests per second: 2.09 [#/sec] (mean)
Time per request: 9579.946 [ms] (mean)
Time per request: 478.997 [ms] (mean, across all concurrent requests)
Transfer rate: 0.93 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 206 392 637.2 250 3325
Processing: 4523 8222 3030.7 8016 13982
Waiting: 208 4798 2958.5 4212 10838
Total: 4813 8614 3120.1 8329 14269

Percentage of the requests served within a certain time (ms)
50% 8329
66% 10851
75% 10998
80% 11128
90% 13933
95% 14056
98% 14189
99% 14223
100% 14269 (longest request)

To perform a "flood" test we set the number of requests (-n) to, say, 5000, and assign the number of concurrent connections{{ (-c}}) to something like 200:

# ab -n 5000 -c 200 http://8.19.73.87/index.html

Benchmarking 8.19.73.87 (be patient)
Finished 316 requests

Server Software: Apache/2.2.3
Server Hostname: 8.19.73.87
Server Port: 80

Document Path: /index.html
Document Length: 283 bytes

Concurrency Level: 1
Time taken for tests: 203.610963 seconds
Complete requests: 316
Failed requests: 0
Write errors: 0
Non-2xx responses: 316
Total transferred: 145992 bytes
HTML transferred: 89428 bytes
Requests per second: 1.55 [#/sec] (mean)
Time per request: 644.338 [ms] (mean)
Time per request: 644.338 [ms] (mean, across all concurrent requests)
Transfer rate: 0.70 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 206 340 509.5 250 3324
Processing: 207 302 450.1 250 7830
Waiting: 206 285 201.5 250 2693
Total: 414 643 683.4 501 8081

Percentage of the requests served within a certain time (ms)
50% 501
66% 505
75% 579
80% 645
90% 651
95% 1313
98% 3648
99% 3649
100% 8081 (longest request)

If the ab output makes you suspect issues, it is useful to look into any replies using tcpdump. In particular, tcp-rst replies could appear. To catch them, use:

# tcpdump -nn 'tcp[tcpflags] == tcp-rst' and port 80

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
10:59:06.036411 IP 89.253.250.50.53261 > 8.19.73.87.80: R 179261015:179261015(0) win 0
10:59:06.036521 IP 89.253.250.50.53261 > 8.19.73.87.80: R 179261015:179261015(0) win 0
10:59:06.036553 IP 89.253.250.50.53261 > 8.19.73.87.80: R 179261016:179261016(0) win 0

We are interested mostly in tcp-rst server replies, as they point to misconfiguration or performance issues. To catch server-side tcp-rst replies use:

# tcpdump -nn 'tcp[tcpflags] == tcp-rst' and port 80 and src host 89.253.250.50

where 89.253.250.50 is the server hosting your tests.

==Referensi==

* https://wiki.appnexus.com/display/documentation/How+to+Apache+Stress+Test+With+ab+Tool