Results for project PHP master, build date 2015-12-17 06:30:09+02:00
commit: 7a01ff5e91983bb1b8fa7bf9e6b115aa99917b64
revision date: 2015-12-17 09:19:05+09:00
environment: Haswell-EP
cpu: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB
mem: 128 GB
os: CentOS 7.1
kernel: Linux 3.10.0-229.4.2.el7.x86_64
Baseline results were generated using release php-7.0.0, with hash
60fffd296abce5fc071f3c173c25a2696cf683c6 from 2015-12-01 04:16:47+00:00
benchmark relative change since change since current rev run
std_dev* last run baseline with PGO
:-| Wordpress 4.2.2 cgi -T10000 0.10% 0.09% 0.37% 7.15%
:-| Drupal 7.36 cgi -T10000 0.16% 0.29% 0.23% 4.39%
:-) MediaWiki 1.23.9 cgi -T5000 0.13% -0.06% 1.50% 2.61%
:-) bench.php cgi -T100 0.01% -0.44% 1.03% 1.63%
:-) micro_bench.php cgi -T10 0.06% 0.05% 1.01% 3.68%
:-) mandelbrot.php cgi -T100 0.02% 1.24% 1.93% 3.00%
Note: Benchmark results for Wordpress, Drupal, MediaWiki are measured in
fetches/second while all others are measured in seconds.
More details on measurements methodology at:
https://01.org/lp/documentation/php-environment-setup.
- Relative Standard Deviation (Standard Deviation/Average)
Our lab does a nightly source pull and build of the PHP project and measures
performance changes against the previous stable version and the previous nightly
measurement. This is provided as a service to the community so that quality
issues with current hardware can be identified quickly.
Intel technologies' features and benefits depend on system configuration and may
require enabled hardware, software or service activation. Performance varies
depending on system configuration.
Hello,
2015-12-17 10:15 GMT+01:00 lp_benchmark_robot@intel.com:
Results for project PHP master, build date 2015-12-17 06:30:09+02:00
commit: 7a01ff5e91983bb1b8fa7bf9e6b115aa99917b64
revision date: 2015-12-17 09:19:05+09:00
environment: Haswell-EP
cpu: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
mem: 128 GB
os: CentOS 7.1
kernel: Linux 3.10.0-229.4.2.el7.x86_64Baseline results were generated using release php-7.0.0, with hash
60fffd296abce5fc071f3c173c25a2696cf683c6 from 2015-12-01 04:16:47+00:00
benchmark relative change since changesince current rev run
std_dev* last run
baseline with PGO
:-| Wordpress 4.2.2 cgi -T10000 0.10% 0.09%
0.37% 7.15%
:-| Drupal 7.36 cgi -T10000 0.16% 0.29%
0.23% 4.39%
:-) MediaWiki 1.23.9 cgi -T5000 0.13% -0.06%
1.50% 2.61%
:-) bench.php cgi -T100 0.01% -0.44%
1.03% 1.63%
:-) micro_bench.php cgi -T10 0.06% 0.05%
1.01% 3.68%
:-) mandelbrot.php cgi -T100 0.02% 1.24%
1.93% 3.00%
Note: Benchmark results for Wordpress, Drupal, MediaWiki are measured in
fetches/second while all others are measured in seconds.
More details on measurements methodology at:
https://01.org/lp/documentation/php-environment-setup.
- Relative Standard Deviation (Standard Deviation/Average)
Our lab does a nightly source pull and build of the PHP project and
measures
performance changes against the previous stable version and the previous
nightly
measurement. This is provided as a service to the community so that quality
issues with current hardware can be identified quickly.Intel technologies' features and benefits depend on system configuration
and may
require enabled hardware, software or service activation. Performance
varies
depending on system configuration.--
Maybe i'm the only one, but in my opinion this mail is rather spam then
helpful.
The results should better be collected in a database and displayed with
helpful graphs or something like that.
A daily mail with no long term change does not really provide a good source
of information.
Best regards
Martin
The results should better be collected in a database and displayed with
helpful graphs or something like that.
A daily mail with no long term change does not really provide a good source
of information.
And just what is it comparing against? A figure against an identical
PHP5.6 version would be of use?
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Hi Martin,
On Thu, Dec 17, 2015 at 7:24 PM, Martin Keckeis
martin.keckeis1@gmail.com wrote:
The results should better be collected in a database and displayed with
helpful graphs or something like that.
A daily mail with no long term change does not really provide a good source
of information.
The objective of this benchmark is to alert developers accidental
performance drop. Even small change may affect performance
a lot. This would be good enough for the purpose. IMO.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net
The objective of this benchmark is to alert developers accidental
performance drop. Even small change may affect performance a lot. This
would be good enough for the purpose. IMO. Regards, -- Yasuo Ohgaki
I would like to see Joomla 3.4.6 and Drupal 8.0 included in this test.
The objective of this benchmark is to alert developers accidental
performance drop. Even small change may affect performance a lot. This
would be good enough for the purpose. IMO. Regards, -- Yasuo OhgakiI would like to see Joomla 3.4.6 and Drupal 8.0 included in this test.
--
Perhaps we could limit it to only send emails if there has been a big
performance drop - that way people would read it rather than dismiss it as
'just todays benchmark email'
-----Original Message-----
From: Chris Riley [mailto:t.carnage@gmail.com]
Sent: Friday, December 18, 2015 12:02 PM
To: Good Guy
Cc: PHP internals
Subject: Re: [PHP-DEV] Benchmark Results for PHP Master 2015-12-17The objective of this benchmark is to alert developers accidental
performance drop. Even small change may affect performance a lot.
This
would be good enough for the purpose. IMO. Regards, -- Yasuo OhgakiI would like to see Joomla 3.4.6 and Drupal 8.0 included in this
test.--
Perhaps we could limit it to only send emails if there has been a big
performance drop - that way people would read it rather than dismiss it
as
'just todays benchmark email'
I suppose there might be persons interested to know if their commits just didn't hurt the performance. If the measurement pulse was not send you will don't know if everything was fine or it wasn't checked at all...
For addressing the legitimate complains we could add a distinctive label in the subject for being able to filter neutral/good/bad performance trends.
Regards,
Bogdan
Am 18.12.2015 14:10 schrieb "Andone, Bogdan" bogdan.andone@intel.com:
-----Original Message-----
From: Chris Riley [mailto:t.carnage@gmail.com]
Sent: Friday, December 18, 2015 12:02 PM
To: Good Guy
Cc: PHP internals
Subject: Re: [PHP-DEV] Benchmark Results for PHP Master 2015-12-17The objective of this benchmark is to alert developers accidental
performance drop. Even small change may affect performance a lot.
This
would be good enough for the purpose. IMO. Regards, -- Yasuo OhgakiI would like to see Joomla 3.4.6 and Drupal 8.0 included in this
test.--
Perhaps we could limit it to only send emails if there has been a big
performance drop - that way people would read it rather than dismiss it
as
'just todays benchmark email'
I suppose there might be persons interested to know if their commits just
didn't hurt the performance. If the measurement pulse was not send you will
don't know if everything was fine or it wasn't checked at all...
For addressing the legitimate complains we could add a distinctive label
in the subject for being able to filter neutral/good/bad performance trends.Regards,
Bogdan
Then add it too the github commit message