Re: [users@httpd] Re: Are this option
Hi again, I tested the settings with Apache Bench ... ab -l -H 'Accept-Encoding: gzip,deflate' -k -n 1 -c 1000 https://www.DOMAIN1.TLD/index.html I'm not sure if the following are good numbers or bad numbers. Can anyone help me interpret this result please? This is ApacheBench, Version 2.3 <$Revision: 1843412 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking www.DOMAIN1.TLD (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed 1 requests Finished 1 requests Server Software:Apache Server Hostname:www.DOMAIN1.TLD Server Port:443 SSL/TLS Protocol: TLSv1.2,ECDHE-RSA-AES128-GCM-SHA256,2048,128 Server Temp Key:X25519 253 bits TLS Server Name:www.DOMAIN1.TLD Document Path: /index.html Document Length:Variable Concurrency Level: 1000 Time taken for tests: 318.542 seconds Complete requests: 1 Failed requests:0 Non-2xx responses: 9572 Keep-Alive requests:9561 Total transferred: 208048597 bytes HTML transferred: 200026656 bytes Requests per second:31.39 [#/sec] (mean) Time per request: 31854.176 [ms] (mean) Time per request: 31.854 [ms] (mean, across all concurrent requests) Transfer rate: 637.82 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect:0 67 283.1 02752 Processing:91 30309 7974.2 33159 49480 Waiting:0 31523 5907.8 33184 49478 Total: 91 30376 7926.5 33162 49480 Percentage of the requests served within a certain time (ms) 50% 33162 66% 33264 75% 33324 80% 33357 90% 33503 95% 33578 98% 33626 99% 33692 100% 49480 (longest request The memory used on the server it's really low ... free -m totalusedfree shared buff/cache available Mem: 643072752 448 196 61106 60683 Swap: 7629 47625 I remind you of the current settings StartServers 2 ServerLimit 45 ThreadLimit 100 ThreadsPerChild 100 MinSpareThreads 100 MaxSpareThreads 750 MaxRequestWorkers 1500 MaxConnectionsPerChild 0 Finally here you have the result of mod_status (very looong) Apache Server Status for 82.x.x.x (via 82.x.x.x) Server Version: Apache/2.4.41 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/1.1.1f Server MPM: event Server Built: 2022-03-16T16:52:53 Current Time: Thursday, 24-Mar-2022 09:06:54 CET Restart Time: Thursday, 24-Mar-2022 09:05:13 CET Parent Server Config. Generation: 1 Parent Server MPM Generation: 0 Server uptime: 1 minute 41 seconds Server load: 6.17 5.45 3.68 Total accesses: 2932 - Total Traffic: 68.5 MB - Total Duration: 66037674 CPU Usage: u15.82 s2.52 cu.97 cs.21 - 19.3% CPU load 29 requests/sec - 0.7 MB/second - 23.9 kB/request - 22523.1 ms/request 1004 requests currently being processed, 396 idle workers Slot PID Stopping Connections Threads Async connections total accepting busy idle writing keep-alive closing 0 245322 no 100 no 100 0 0 0 0 1 247187 no 100 no 100 0 0 0 0 2 245581 no 100 no 100 0 0 0 0 3 245737 no 100 no 100 0 0 0 0 4 245738 no 100 no 100 0 0 0 0 5 245991 no 99 yes 99 1 0 0 0 6 245992 no 100 no 100 0 0 0 0 7 247321 no 100 no 100 0 0 0 0 8 245994 no 100 no 100 0 0 0 0 9 247322 no 100 no 100 0 0 0 0 10 247565 no 0 yes 0 100 0 0 0 11 247566 no 0 yes 0 100 0 0 0 12 247570 no 1 yes 2 98 0 0 0 13 247582 no 3 yes 3 97 0 0 0 Sum 14 0 1003 1004 396 0 0 0 WW_W __
Re: [users@httpd] Re: Are this option
On Thu, Mar 24, 2022 at 9:36 AM Marc Serra wrote: > > I tested the settings with Apache Bench ... > > ab -l -H 'Accept-Encoding: gzip,deflate' -k -n 1 -c 1000 > https://www.DOMAIN1.TLD/index.html > > I'm not sure if the following are good numbers or bad numbers. Can > anyone help me interpret this result please? Pretty bad numbers actually, aren't you limited by the network bandwidth between ab and the server? What are the numbers from ab when it's running on the server (i.e. ab ... https://localhost/index.html)? The CPU usage looks high (20%) too for the requested load, but that's probably on mod_deflate (and TLS handshakes), how does "-H 'Accept-Encoding: gzip,deflate'" change things? Sorry, more questions than answers, but results on my (poor) laptop look like: $ bin/ab -k -n 1 -c 1000 https://localhost:40443/250KB.bin ... Server Software:Apache/2.5.1-dev Server Hostname:localhost Server Port:40443 SSL/TLS Protocol: TLSv1.2,ECDHE-RSA-AES256-GCM-SHA384,2048,256 Server Temp Key:X25519 253 bits Document Path: /250KB.bin Document Length:256000 bytes Concurrency Level: 1000 Concurrency achieved: 1000 Rampup delay: 0 [ms] Time taken for tests: 2.437 seconds Complete requests: 1 Failed requests:0 Keep-Alive requests:1 Total transferred: 2607109000 bytes HTML transferred: 2603564800 bytes Requests per second:4103.52 [#/sec] (mean) Time per request: 243.694 [ms] (mean) Time per request: 0.244 [ms] (mean, across all concurrent requests) Transfer rate: 1044756.99 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect:0 34 103.0 0 378 Processing: 181 203 9.6203 527 Waiting:0 13 6.9 10 152 Total:181 237 105.3203 579 Percentage of the requests served within a certain time (ms) 50%203 66%206 75%209 80%212 90%517 95%552 98%563 99%567 100%579 (longest request) Or with a shorter resource (1KB) and 10x more requests to amortize the ramp up: $ bin/ab -k -n 10 -c 1000 https://localhost:40443/1KB.bin ... Concurrency Level: 1000 Concurrency achieved: 1000 Rampup delay: 0 [ms] Time taken for tests: 1.953 seconds Complete requests: 10 Failed requests:0 Keep-Alive requests:99475 Total transferred: 135073187 bytes HTML transferred: 103209984 bytes Requests per second:51202.91 [#/sec] (mean) Time per request: 19.530 [ms] (mean) Time per request: 0.020 [ms] (mean, across all concurrent requests) Transfer rate: 67540.43 [Kbytes/sec] received Regards; Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Re: Are this option
> Pretty bad numbers actually, aren't you limited by the network > bandwidth between ab and the server? I think it isn't a bandwidth problem. Look ... wget https://domain.tld/test.zip --2022-03-24 12:04:26-- https://domain.tld/test.zip Resolving domain.tld (domain.tld)... 82.x.x.x Connecting to domain.tld (domain.tld)|82.x.x.x|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 688466403 (657M) [application/zip] Saving to: ‘test.zip’ test.zip 100%[===>] 656.57M 11.2MB/sin 59s 2022-03-24 12:05:25 (11.2 MB/s) - ‘test.zip’ saved [688466403/688466403] > What are the numbers from ab when it's running on the server (i.e. ab > ... https://localhost/index.html)? Not good (this test is made from the same server where are hosted www.domain.tld) ... ab -l -H 'Accept-Encoding: gzip,deflate' -k -n 1 -c 1000 https://www.domain.tld/index.html This is ApacheBench, Version 2.3 <$Revision: 1843412 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking www.domain.tld (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed 1 requests Finished 1 requests Server Software:Apache Server Hostname:www.domain.tld Server Port:443 SSL/TLS Protocol: TLSv1.2,ECDHE-RSA-AES128-GCM-SHA256,2048,128 Server Temp Key:X25519 253 bits TLS Server Name:www.domain.tld Document Path: /index.html Document Length:Variable Concurrency Level: 1000 Time taken for tests: 262.963 seconds Complete requests: 1 Failed requests:0 Non-2xx responses: 9582 Keep-Alive requests:9582 Total transferred: 57837957 bytes HTML transferred: 49816818 bytes Requests per second:38.03 [#/sec] (mean) Time per request: 26296.304 [ms] (mean) Time per request: 26.296 [ms] (mean, across all concurrent requests) Transfer rate: 214.79 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect:0 292 1179.6 08078 Processing: 0 24796 6927.5 27341 54249 Waiting:0 25726 5596.4 27377 54249 Total: 0 25088 6821.9 27372 54249 Percentage of the requests served within a certain time (ms) 50% 27372 66% 27532 75% 27641 80% 27767 90% 28015 95% 28133 98% 31766 99% 40137 100% 54249 (longest request > The CPU usage looks high (20%) too for the requested load, but that's > probably on mod_deflate (and TLS handshakes), how does "-H > 'Accept-Encoding: gzip,deflate'" change things? I tried without the -H option and I got similar results ab -l -k -n 1 -c 1000 https://www.domain.tld/index.php This is ApacheBench, Version 2.3 <$Revision: 1843412 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking www.domain.tld (be patient) Completed 1000 requests Completed 2000 requests Completed 3000 requests Completed 4000 requests Completed 5000 requests Completed 6000 requests Completed 7000 requests Completed 8000 requests Completed 9000 requests Completed 1 requests Finished 1 requests Server Software:Apache Server Hostname:www.domain.tld Server Port:443 SSL/TLS Protocol: TLSv1.2,ECDHE-RSA-AES128-GCM-SHA256,2048,128 Server Temp Key:X25519 253 bits TLS Server Name:www.domain.tld Document Path: /index.php Document Length:Variable Concurrency Level: 1000 Time taken for tests: 325.617 seconds Complete requests: 1 Failed requests:0 Keep-Alive requests:0 Total transferred: 157188 bytes HTML transferred: 156440 bytes Requests per second:30.71 [#/sec] (mean) Time per request: 32561.691 [ms] (mean) Time per request: 32.562 [ms] (mean, across all concurrent requests) Transfer rate: 4714.25 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect:1 177 610.2 23500 Processing: 334 30715 5844.0 32449 48394 Waiting: 218 30593 5846.3 32327 48264 Total:336 30892 5586.1 32456 48396 Percentage of the requests served within a certain time (ms) 50% 32456 66% 32616 75% 32700 80% 32733 90% 32833 95% 32934 98% 33002 99% 33033 100% 48396 (longest request) > Sorry, more questions than answers, but results on my (poor) laptop look like: Oh, no! Thank's for all your answers, questions and time! > Or with a shorter resource (1KB) and 10x more requests to amortize the ramp > up: -- Marc Serra --
Re: [users@httpd] Re: Are this option
Please don't spend more time on this until I write another email. I found sometrhng strange on our PHP code. Missatge de Marc Serra del dia dj., 24 de març 2022 a les 12:42: > > > Pretty bad numbers actually, aren't you limited by the network > > bandwidth between ab and the server? > > I think it isn't a bandwidth problem. Look ... > > wget https://domain.tld/test.zip > --2022-03-24 12:04:26-- https://domain.tld/test.zip > Resolving domain.tld (domain.tld)... 82.x.x.x > Connecting to domain.tld (domain.tld)|82.x.x.x|:443... connected. > HTTP request sent, awaiting response... 200 OK > Length: 688466403 (657M) [application/zip] > Saving to: ‘test.zip’ > > test.zip > 100%[===>] > 656.57M 11.2MB/sin 59s > > 2022-03-24 12:05:25 (11.2 MB/s) - ‘test.zip’ saved [688466403/688466403] > > > > What are the numbers from ab when it's running on the server (i.e. ab > > ... https://localhost/index.html)? > > Not good (this test is made from the same server where are hosted > www.domain.tld) ... > > ab -l -H 'Accept-Encoding: gzip,deflate' -k -n 1 -c 1000 > https://www.domain.tld/index.html > This is ApacheBench, Version 2.3 <$Revision: 1843412 $> > Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ > Licensed to The Apache Software Foundation, http://www.apache.org/ > > Benchmarking www.domain.tld (be patient) > Completed 1000 requests > Completed 2000 requests > Completed 3000 requests > Completed 4000 requests > Completed 5000 requests > Completed 6000 requests > Completed 7000 requests > Completed 8000 requests > Completed 9000 requests > Completed 1 requests > Finished 1 requests > > > Server Software:Apache > Server Hostname:www.domain.tld > Server Port:443 > SSL/TLS Protocol: TLSv1.2,ECDHE-RSA-AES128-GCM-SHA256,2048,128 > Server Temp Key:X25519 253 bits > TLS Server Name:www.domain.tld > > Document Path: /index.html > Document Length:Variable > > Concurrency Level: 1000 > Time taken for tests: 262.963 seconds > Complete requests: 1 > Failed requests:0 > Non-2xx responses: 9582 > Keep-Alive requests:9582 > Total transferred: 57837957 bytes > HTML transferred: 49816818 bytes > Requests per second:38.03 [#/sec] (mean) > Time per request: 26296.304 [ms] (mean) > Time per request: 26.296 [ms] (mean, across all concurrent requests) > Transfer rate: 214.79 [Kbytes/sec] received > > Connection Times (ms) > min mean[+/-sd] median max > Connect:0 292 1179.6 08078 > Processing: 0 24796 6927.5 27341 54249 > Waiting:0 25726 5596.4 27377 54249 > Total: 0 25088 6821.9 27372 54249 > > Percentage of the requests served within a certain time (ms) > 50% 27372 > 66% 27532 > 75% 27641 > 80% 27767 > 90% 28015 > 95% 28133 > 98% 31766 > 99% 40137 > 100% 54249 (longest request > > > > The CPU usage looks high (20%) too for the requested load, but that's > > probably on mod_deflate (and TLS handshakes), how does "-H > > 'Accept-Encoding: gzip,deflate'" change things? > > I tried without the -H option and I got similar results > > ab -l -k -n 1 -c 1000 https://www.domain.tld/index.php > This is ApacheBench, Version 2.3 <$Revision: 1843412 $> > Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ > Licensed to The Apache Software Foundation, http://www.apache.org/ > > Benchmarking www.domain.tld (be patient) > Completed 1000 requests > Completed 2000 requests > Completed 3000 requests > Completed 4000 requests > Completed 5000 requests > Completed 6000 requests > Completed 7000 requests > Completed 8000 requests > Completed 9000 requests > Completed 1 requests > Finished 1 requests > > > Server Software:Apache > Server Hostname:www.domain.tld > Server Port:443 > SSL/TLS Protocol: TLSv1.2,ECDHE-RSA-AES128-GCM-SHA256,2048,128 > Server Temp Key:X25519 253 bits > TLS Server Name:www.domain.tld > > Document Path: /index.php > Document Length:Variable > > Concurrency Level: 1000 > Time taken for tests: 325.617 seconds > Complete requests: 1 > Failed requests:0 > Keep-Alive requests:0 > Total transferred: 157188 bytes > HTML transferred: 156440 bytes > Requests per second:30.71 [#/sec] (mean) > Time per request: 32561.691 [ms] (mean) > Time per request: 32.562 [ms] (mean, across all concurrent requests) > Transfer rate: 4714.25 [Kbytes/sec] received > > Connection Times (ms) > min mean[+/-sd] median max > Connect:1 177 610.2 23500 > Processing: 334 30715 5844.0 32449 48394 > Waiting: 218 30593 5846.3 32327 48264 > Total:336 30892 5586.1 32456 48396 > > Percentage of the r
