Re: @@Jit Attribute Considerations
| From: | Peter Bowyer | Date: | Mon, 03 Aug 2020 19:39:32 +0000 |
| Subject: | Re: @@Jit Attribute Considerations | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-111303@lists.php.net to get a copy of this message | ||
On Mon, 3 Aug 2020 at 19:52, Stanislav Malyshev <smalyshev@gmail.com> wrote:
> I think turning JIT off is a valid use case, the rest looks much more
> iffy. I am not sure we want to let people tell the engine to JIT certain
> functions - are there a lot of cases where the engine wouldn't do it but
> it's actually the right thing to do?
>
Wouldn't a use case be profiling code, to see if JIT makes a difference to
a specific function? So I can profile with JIT disabled globally and @@JIT
on specific code, modify my code and see if it improves the JIT performance?
I'm basing this on my experience with the @jit annotation in Numba (
http://numba.pydata.org/) where it's useful to see the
effect on small
pieces of code.
Peter