We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm not sure if this is really necessary in vanilla PHP, at least it won't hurt. HHVM uses a JIT and would benefit from a warm up phase.
The text was updated successfully, but these errors were encountered:
Does instructing the HHVM JIT to perform an immediate warm-up help?
hhvm -v Eval.Jit=1 -v Eval.JitProfileInterpRequests=0 ./vendor/bin/athletic -p ./tests/
Note: If using HHVM < 3.4, change Eval.JitProfileInterpRequests to Eval.JitWarmupRequests.
Eval.JitProfileInterpRequests
Eval.JitWarmupRequests
Sorry, something went wrong.
Regardless, PHP 7 has an experimental JIT, so a general purpose warm-up specification might work out just fine. Something like:
/** * @iterations 1000, 10 */
++, someone want to send a PR? I'm pretty hands-off on this library nowadays
Even if vanilla PHP doesn't JIT anything, it'd help prime CPU caches, OS page cache, etc.
No branches or pull requests
I'm not sure if this is really necessary in vanilla PHP, at least it won't hurt. HHVM uses a JIT and would benefit from a warm up phase.
The text was updated successfully, but these errors were encountered: