-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
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
Add experimental flag to enable YJIT compiler #270
Conversation
Authored-by: Seth Boyles <sboyles@pivotal.io>
we may want to separate the config flag into separate flags per job, so you can just enable the API server with YJIT, for example |
Has this functionality ever been tested? I'm wondering how this would have worked given the fact that the ruby package provided by the bosh-packages-ruby-release does not pass the |
AFAIK the https://github.com/ruby/ruby/blob/ruby_3_1/doc/yjit/yjit.md
vs 3.2:
So, yeah, I had verified this was working with Ruby 3.1 by checking the logs (just printing Ruby version to see the |
you can also check this yourself by installing ruby 3.1 and 3.2 and running 3.1
3.2
|
Thanks @sethboyles, that's great context to have, I did not know that the rust dependency was introduced later. |
enables YJIT compiler on CC jobs.
YJIT is optimized for long running processes, trading a higher memory usage for speed improvements.
Most of the jobs worked fine without alteration with default config values, but I did have to bump up the memory thresholds on the cc-worker.
for more on running YJIT:
https://github.com/ruby/ruby/blob/master/doc/yjit/yjit.md
https://news.ycombinator.com/item?id=29161810
I have viewed signed and have submitted the Contributor License Agreement
I have made this pull request to the
develop
branchI have run CF Acceptance Tests on bosh lite