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
Summary
As the JIT in postgresql, now that, we also can support JIT in ShannonBase for rapid engine.
Do we really need to support this feature or not? Probably not.
ref: [1] Just in Time Compilation: https://web.archive.org/web/20180503145240/http://www.cs.columbia.edu/~aho/cs6998/Lectures/14-09-22_Croce_JIT.pdf [2] JIT in PostgreSQL: https://www.postgresql.org/docs/current/jit-reason.html
The text was updated successfully, but these errors were encountered:
Is it a good idea to support JIT in mysql?
Sorry, something went wrong.
ShannonBase
No branches or pull requests
Summary
As the JIT in postgresql, now that, we also can support JIT in ShannonBase for rapid engine.
Do we really need to support this feature or not? Probably not.
ref:
[1] Just in Time Compilation: https://web.archive.org/web/20180503145240/http://www.cs.columbia.edu/~aho/cs6998/Lectures/14-09-22_Croce_JIT.pdf
[2] JIT in PostgreSQL: https://www.postgresql.org/docs/current/jit-reason.html
The text was updated successfully, but these errors were encountered: