I want to test the performance of my apache with AB (Apache Benchemark) with parameter authentication.
I followed this tutorial step
Using Apache Benchmark (ab) on sites with authentication
and when I execute the command
ab-c 1-n 1-C PHPSESSID = 65pnirttcbn0l6seutjkf28452 http://my-web-site
but authentication does not pass
testeur#ERP:~$ ab -c 1 -n 1 -C PHPSESSID=65pnirttcbn0l6seutjkf28452 http:my-web-site.com/mapviewimproved
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, `http://www.zeustech.net/`
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking my-web-site.com (be patient).....done
Server Software: Apache
Server Hostname: algeotrack.com
Server Port: 80
Document Path: /my-page
Document Length: 0 bytes
Concurrency Level: 1
Time taken for tests: 0.627 seconds
Complete requests: 1
Failed requests: 0
Write errors: 0
Non-2xx responses: 1
Total transferred: 335 bytes
HTML transferred: 0 bytes
Requests per second: 1.59 [#/sec] (mean)
Time per request: 627.320 [ms] (mean)
Time per request: 627.320 [ms] (mean, across all concurrent requests)
Transfer rate: 0.52 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 36 36 0.0 36 36
Processing: 591 591 0.0 591 591
Waiting: 591 591 0.0 591 591
Total: 627 627 0.0 627 627
I note that the application is developed with Zend Framework 1
is that you can help me please
You have to quote the cookie value:
ab -c 1 -n 1 -C 'PHPSESSID=65pnirttcbn0l6seutjkf28452' http:my-web-site.com/mapviewimproved
see this other question as reference: How do I pass a complex cookie to ab for testing?
Related
My team has a project which is not too big, built by make -js, cost 40 seconds, when using bazel, the time incresed to 70 secs. And here is the profile of the build process of bazel. I noticed that SKYFUNCTION takes 47% of the time cost, is that reasonable?
PROFILES
the last section of it:
Type Total Count Average
ACTION 0.03% 77 0.70 ms
ACTION_CHECK 0.00% 4 0.90 ms
ACTION_EXECUTE 40.40% 77 912 ms
ACTION_UPDATE 0.00% 74 0.02 ms
ACTION_COMPLETE 0.19% 77 4.28 ms
INFO 0.00% 1 0.05 ms
VFS_STAT 1.07% 117519 0.02 ms
VFS_DIR 0.27% 4613 0.10 ms
VFS_MD5 0.22% 151 2.56 ms
VFS_DELETE 4.43% 53830 0.14 ms
VFS_OPEN 0.01% 232 0.11 ms
VFS_READ 0.06% 3523 0.03 ms
VFS_WRITE 0.00% 4 0.97 ms
WAIT 0.05% 156 0.56 ms
SKYFRAME_EVAL 6.23% 1 10.830 s
SKYFUNCTION 47.01% 687 119 ms
#ittai, #Jin, #Ondrej K, I have tried to switched off the sandboxing in bazel, it seems much faster than with it switched on. here is the comparison:
SWITCHED ON: 70s
SWITCHED OFF: 33s±2
the skyFunction still takes 47% of all the execution time. but the everage times it takes turned from 119ms to 21ms.
IHi I have the same question as JMeter: jp#gc Graphs Generator: I got .png just with text "Waiting for sample...". The jtl file has been created without empty line, have edited the user.properties file.
I followed the steps mentioned in this link for the graph generator.
sh jmeter -t /home/Annie/JMeter/grp.jmx -n -l /home/Annie/JMeter/g.jtl -JTEST_RESULTS_FILE=/home/Annie/JMeter/g.jtl
Creating summariser <summary>
Created the tree successfully using /home/Annie/JMeter/grp.jmx
Starting the test # Mon Oct 16 11:27:30 IST 2017 (1508133450438)
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
summary + 1 in 00:00:03 = 0.3/s Avg: 3133 Min: 3133 Max: 3133 Err: 0 (0.00%) Active: 2 Started: 2 Finished: 0
summary + 14 in 00:00:14 = 1.0/s Avg: 2731 Min: 2098 Max: 4216 Err: 0 (0.00%) Active: 0 Started: 5 Finished: 5
summary = 15 in 00:00:18 = 0.9/s Avg: 2757 Min: 2098 Max: 4216 Err: 0 (0.00%)
Tidying up ... # Mon Oct 16 11:27:48 IST 2017 (1508133468522)
... end of run
In log its showing :
WARN o.a.j.v.ViewResultsFullVisualizer:Error loading result renderer: org.apache.jmeter.visualizers.RenderInBrowser
java.lang.NoClassDefFoundError: javafx/embed/swing/JFXPanel
Caused by: java.lang.ClassNotFoundException: javafx.embed.swing.JFXPanel
What should be done to get the graph?
My expectation is that you are using OpenJDK on Linux which doesn't have JavaFX
Use your Linux distribution package manager to get Oracle Java 8 and make sure JMeter is configured to use Oracle Java instead of OpenJDK.
If you are trying to use PerfMon Metrics Collector Listener in GUI mode to test it - make sure JMeter test is running at this time as first of all it is a Listener therefore it needs to process sample events in order to display anything, it might be even a Dummy Sampler firing each N seconds. See How to Monitor Your Server Health & Performance During a JMeter Load Test guide for more details.
When I run the command given on the meteor website:
curl https://install.meteor.com/ | sh
I get as follows:
curl: (6) Could not resolve host: meteorinstall-4168.kxcdn.com
when I run:
ping meteorinstall-4168.kxcdn.com
I get:
Request timeout for icmp_seq 30
64 bytes from 161.202.39.238: icmp_seq=31 ttl=51 time=182.303 ms
Request timeout for icmp_seq 32
64 bytes from 161.202.39.238: icmp_seq=33 ttl=51 time=181.406 ms
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
64 bytes from 161.202.39.238: icmp_seq=36 ttl=51 time=186.054 ms
64 bytes from 161.202.39.238: icmp_seq=37 ttl=51 time=182.544 ms
Request timeout for icmp_seq 38
64 bytes from 161.202.39.238: icmp_seq=39 ttl=51 time=186.920 ms
Request timeout for icmp_seq 40
What should I do?
If you try again, this should work now. Meteor 1.4.1.1 was accidentally not published properly before the 1.4.1.1 release number was recommended. New downloads were broken until sometime yesterday (you can see the full details in issue 7697).
I'm trying to install the ixgbevf on a Amazon EC2 CentOS7 instance. The steps looks good, but everytime when I run the instance in a Enhanced Networking enabled type, such as M4.xlarge, the network seems fail(I can not connect to the instance after startup).
Here's what I did:
wget http://elrepo.org/linux/elrepo/el7/x86_64/RPMS/kmod-ixgbevf-2.16.1-1.el7.elrepo.x86_64.rpm
rpm -ivh kmod-ixgbevf-2.16.1-1.el7.elrepo.x86_64.rpm
cp -p /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak
dracut -f
Then shutdown the instance, and set the sriov
ec2-modify-instance-attribute instance_id --sriov simple
That all. Whenever the type(such as T2.micro) doesn't support Enhanced Networking, the instance works fine. But if I change the type to Enhanced Networking enabled(such as M4.xlarge), the instance simply can't be accessed. Anyone have any idea about this? Did I miss something?
The answer lies buried into this section of the original documentation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux
In a nutshell, CentOS 7 already ships with the ixgbevf module, although not with the latest version, but this is hardly a problem. What was causing my instance to be unreachable after a reboot were the "predictable network interfaces", enabled by default.
To disable them, simply visit that link, jump straight to step number 6 and type:
$ rpm -qa | grep -e '^systemd-[0-9]\+\|^udev-[0-9]\+'
$ sudo sed -i '/^GRUB\_CMDLINE\_LINUX/s/\"$/\ net\.ifnames\=0\"/' /etc/default/grub
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
After that:
Stop the instance
Enable the Enhanced Networking via the aws CLI
Restart it
You should now be able to log in!
On Oracle Linux 6.9 (same as RHEL6/CENTOS6), in a aws placement group running iperf3 between two r2.xlarge instances, i got just shy of 2.5Gbps. ethtools reports vif but the ixgbevf driver is installed. Without SRIOV set to simple, most instances seem to get 1Gbps max.
[ 4] local 10.11.5.61 port 52754 connected to 10.11.5.222 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 268 MBytes 2.25 Gbits/sec 56 559 KBytes
[ 4] 1.00-2.00 sec 296 MBytes 2.48 Gbits/sec 54 629 KBytes
[ 4] 2.00-3.00 sec 296 MBytes 2.48 Gbits/sec 61 551 KBytes
[ 4] 3.00-4.00 sec 296 MBytes 2.48 Gbits/sec 62 454 KBytes
[ 4] 4.00-5.00 sec 296 MBytes 2.48 Gbits/sec 55 551 KBytes
[ 4] 5.00-6.00 sec 288 MBytes 2.42 Gbits/sec 50 454 KBytes
[ 4] 6.00-7.00 sec 291 MBytes 2.44 Gbits/sec 55 559 KBytes
[ 4] 7.00-8.00 sec 296 MBytes 2.48 Gbits/sec 55 507 KBytes
[ 4] 8.00-9.00 sec 296 MBytes 2.48 Gbits/sec 60 472 KBytes
[ 4] 9.00-10.00 sec 296 MBytes 2.48 Gbits/sec 59 559 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 2.85 GBytes 2.45 Gbits/sec 567 sender
[ 4] 0.00-10.00 sec 2.85 GBytes 2.45 Gbits/sec receiver
Note speeds are slower between different familys even in a placement group as they may have to be placed on different machines.
You can also look at adding ENA interfaces to see if you get better speeds on m4 and c4 instances. Also this is the only support networking on newer instance types m5 and c5.
I've been looking for days to see if someone has done a good, documented, PHP processing speed comparison between
apache-mpm-prefork 2.4 with mod_php 5.4
and
nginx 1.2.x + PHP-FPM 5.4
Why I'm looking: The only test I saw are abount benchmarks, serving full pages or Hello, World -like test, without proper documentation on what exactly was tested. I don't care about the request/seconds, the hardware, but I do need to see what PHP script was tested and with what exact configuration.
Why these two: mod_php was known to be the fastest on processing PHP ( no static files, no request/response measuring, just processing the PHP itself ) but a lot has changed since then, including apache version. Nginx and PHP-FPM eats a lot less memory, so it'd be a good reason to change architecture but if they're not fast enough in this case, the change would be irrelevant.
I know if I'm unable to find one I have to do it myself but I can't believe no one has done a test like this so far :)
I have completed this test on CentOS 6.3 using nginx 1.2.7, apache 2.4.3 and php 5.4.12 all compiled with no changes to default.
./configure
make && make install
With the exception of php where I enabled php-fpm
./configure --enable-fpm
All servers have 100% default config except as noted below. All testing was done on a test server, with no load and a reboot between tests. The server has a Intel(R) Xeon(R) CPU E3-1230, 1GB RAM and 2 x 60GB SSD in RAID 1. Tests were run using ab -n 50000 -c 500 http://127.0.0.1/test.php
Test PHP script:
<?php
$testing = 0;
for ($i = 0; $i < 1000; $i++) {
$testing++;
}
echo $testing;
I also had to enable php in nginx.conf as it's not enabled by default.
location ~ \.php$ {
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME /var/www/html$fastcgi_script_name;
include fastcgi_params;
}
Nginx - PHP-FPM on 127.0.0.1:9000
Concurrency Level: 500
Time taken for tests: 10.932 seconds
Complete requests: 50000
Failed requests: 336
(Connect: 0, Receive: 0, Length: 336, Exceptions: 0)
Write errors: 0
Non-2xx responses: 336
Total transferred: 7837824 bytes
HTML transferred: 379088 bytes
Requests per second: 4573.83 [#/sec] (mean)
Time per request: 109.317 [ms] (mean)
Time per request: 0.219 [ms] (mean, across all concurrent requests)
Transfer rate: 700.17 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 34 338.5 0 7000
Processing: 0 34 166.5 23 8120
Waiting: 0 34 166.5 23 8120
Total: 13 68 409.2 23 9846
Percentage of the requests served within a certain time (ms)
50% 23
66% 28
75% 32
80% 33
90% 34
95% 46
98% 61
99% 1030
100% 9846 (longest request)
Nginx - PHP-FPM via socket (config change to fastcgi_pass)
fastcgi_pass unix:/var/lib/php/php.sock;
Concurrency Level: 500
Time taken for tests: 7.054 seconds
Complete requests: 50000
Failed requests: 351
(Connect: 0, Receive: 0, Length: 351, Exceptions: 0)
Write errors: 0
Non-2xx responses: 351
Total transferred: 7846209 bytes
HTML transferred: 387083 bytes
Requests per second: 7087.70 [#/sec] (mean)
Time per request: 70.545 [ms] (mean)
Time per request: 0.141 [ms] (mean, across all concurrent requests)
Transfer rate: 1086.16 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 26 252.5 0 7001
Processing: 0 24 112.9 17 3683
Waiting: 0 24 112.9 17 3683
Total: 7 50 306.4 17 7001
Percentage of the requests served within a certain time (ms)
50% 17
66% 19
75% 20
80% 21
90% 23
95% 31
98% 55
99% 1019
100% 7001 (longest request)
Apache - mod_php
Concurrency Level: 500
Time taken for tests: 10.979 seconds
Complete requests: 50000
Failed requests: 0
Write errors: 0
Total transferred: 9800000 bytes
HTML transferred: 200000 bytes
Requests per second: 4554.02 [#/sec] (mean)
Time per request: 109.793 [ms] (mean)
Time per request: 0.220 [ms] (mean, across all concurrent requests)
Transfer rate: 871.67 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 22 230.2 1 7006
Processing: 0 58 426.0 18 9612
Waiting: 0 58 425.9 18 9611
Total: 5 80 523.8 19 10613
Percentage of the requests served within a certain time (ms)
50% 19
66% 23
75% 25
80% 26
90% 31
95% 36
98% 1012
99% 1889
100% 10613 (longest request)
I'll be more than happy to tune apache further, but it seems apache just can't keep up. The clear winner is nginx with php-fpm via socket.
It seems you are comparing apples with oranges, or more to put it more accurately, you are confounding the results by adjusting two variables. Surely, it would be more sensible to compare Apache+fastcgi+php-fpm against nginx+php-fpm? You'd expect the php-fpm part to be the same, so then you would be measuring the better of Apache_fastcgi vs nginx.