Composer is a terrible benchmark for JIT.
Composer is highly IO and network dependant and doesn’t do a lot of math or loops.
JIT is completely useless for this case, and the volatility of networks never provides a stable repeatable benchmark.
I was wondering about the JIT in CLI applications – JIT only works with opcache enabled, but does it work when only the file opcache is enabled, and how does it work, does it change the generated opcache files over time (optimizing them), as there is no shared memory between multiple CLI executions, or am I thinking about it wrongly?
I have not found a good tutorial on how to best configure JIT for CLI applications, and PHP itself has no documentation about this so far (as far as I can find anything), so I wouldn’t even know how to run CLI applications with JIT the best way, or even in a way that would make use of JIT.
I’m pretty sure you need to set opcache.enable_cli = 1 but I haven’t played around with it much. We have a usecase for it, but when we played with it a few weeks ago with the RCs, the script died from memory usage when JIT was enabled. Seems like JIT causes scripts to use way more memory but I don’t have enough evidence to say that with any level of certainty.
Members
Online