and with a demo-page containing all sort of modules and bloat the
difference is even greater - can't wait to see that in production
is there anything known when it is expected to arrive in the official
tree or does Zend even hold it back until the point when they can
suprise with a "we are done, all tests are fine and we can merge it"
announce?
PHP 7.1:
Requests per second: 316.77 [#/sec] (mean)
Time per request: 157.844 [ms] (mean)
Time per request: 3.157 [ms] (mean, across all concurrent requests)
Transfer rate: 12604.11 [Kbytes/sec] received
PHP 7.2 JIT:
Requests per second: 925.96 [#/sec] (mean)
Time per request: 53.998 [ms] (mean)
Time per request: 1.080 [ms] (mean, across all concurrent requests)
Transfer rate: 36842.68 [Kbytes/sec] received
Am 02.05.2017 um 18:00 schrieb li...@rhsoft.net:
https://github.com/zendtech/php-src/tree/jit-dynasm/ext/opcache/jit
that below is a "ab -c 50 -n 100000" on a Intel(R) Core(TM) i7-3770 CPU
@ 3.40GHz on our core cms (pgo-build with heavy compiler optimizations,
only the source tarball deifferent)
currently our production 2x6 core machine with two Intel(R) Xeon(R) CPU
E5-2643 v3 @ 3.40GHz and the same setup is around 4000-5000 per second
which is nearly reached by the 6 years old i7 with the JIT
impressive!
JIT:
Requests per second: 3526.56 [#/sec] (mean)
Time per request: 14.178 [ms] (mean)
Time per request: 0.284 [ms] (mean, across all concurrent requests)
7.1:
Requests per second: 1419.87 [#/sec] (mean)
Time per request: 35.214 [ms] (mean)
Time per request: 0.704 [ms] (mean, across all concurrent requests)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
