Re: the experimental jit-branch is impressive

On Tue, May 2, 2017 at 9:04 PM, lists@rhsoft.net <lists@rhsoft.net> wrote: > > Am 02.05.2017 um 20:53 schrieb Nikita Popov: > >> These results are very unlikely. I'm 95% sure your benchmark is >> broken. My first guess would be that you're benchmarking PHP + >> JIT against PHP without opcache. Please share the relevant >> (opcache-related) portion of the php.inis you used >> >> no they are not - since i build RPM packages and even the whole >> spec-file is unchanged, only the tarball changed and the build is >> highly optimized i can assure you for 100% that i compare PHP >> 7.1.5RC1 with https://github.com/zendtech/php-src >> <https://github.com/zendtech/php-src> downloaded >> today >> >> maybe the PGO-profiling running autotests and fuzzy-calls on the >> whole application as well as 2000 cms-requests combined with the >> compiler flags improves the JIT itself >> >> without opcache the results for 7.1.5 are *dramatically* slower >> >> and i repeated the test upgrade/downgrade packages and run "ab" >> multiple times on that machine - attached the "php.spec" which is >> used for the build >> >> in just downloaded the zip from >> https://github.com/zendtech/php-src >> <https://github.com/zendtech/php-src>, renamed it >> to "php-7.2.0", >> made a tar.xz archive, changed the version on teh frist line in the >> spec file and fired the build/profiling - nothing else changed >> > > > >> You have xdebug enabled... >> > > loaded, but not enabled > > xdebug.default_enable = 0 > xdebug.profiler_enable = 0 > xdebug.profiler_enable_trigger = 1 > > 7.1.5: Requests per second: 136.46 > 7.1.5 opcache: Requests per second: 316.77 > 7.2.0 JIT PGO: Requests per second: 925.96 > 7.2.0 JIT NON-PGO: Requests per second: 849.99 > > around 8% are the difference with or without PGO, no idea how much > strict-types and a 100% typehinted codebase makes a difference to the JIT > operations > This is a common misconception. If you have loaded xdebug you will incur a major performance hit, regardless of ini settings. xdebug.default_enable is a badly named option, which controls display of stack traces, not whether xdebug is enabled. As far as I know, there is no way to disable xdebug once it has been loaded. Please unload xdebug and try again. Nikita