Skip to content
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

Evaluate if CC runs Ruby 3.X #2619

Closed
1 task done
FloThinksPi opened this issue Jan 12, 2022 · 3 comments
Closed
1 task done

Evaluate if CC runs Ruby 3.X #2619

FloThinksPi opened this issue Jan 12, 2022 · 3 comments
Labels
performance PoC Issue/PR that is part of a PoC to try out new things

Comments

@FloThinksPi
Copy link
Member

FloThinksPi commented Jan 12, 2022

Issue

Different sources claim alternative ruby implementations as well as CRuby 3.x do have a positive performance impact on rails applications that can be quite substantial.

Context

See https://eregon.me/blog/2022/01/06/benchmarking-cruby-mjit-yjit-jruby-truffleruby.html for reference to a benchmark comparing multiple ruby interpreters also with a rails application benchmark.

We should try out some of them firstly if they work and also if they improve overall performance in a mensurabel way.
Especially as CRuby 3.1 includes https://github.com/Shopify/yjit which promises improvements without loosing compatibility at all.

Acceptance Criteria

  • Have a branch of CC_NG that runs with CRuby 3.x and preferably yjit
@FloThinksPi FloThinksPi added performance PoC Issue/PR that is part of a PoC to try out new things labels Jan 12, 2022
@sethboyles
Copy link
Member

Thanks for linking that blog post. Would be very interesting to see if we can get comparable perf improvements from Truffleruby.

@sethboyles
Copy link
Member

see #2623 for a WIP on the Ruby 3 upgrade

@FloThinksPi FloThinksPi linked a pull request Jan 13, 2022 that will close this issue
12 tasks
sethboyles added a commit that referenced this issue Feb 28, 2022
[#2619]

Co-authored-by: Seth Boyles <sboyles@pivotal.io>
Co-authored-by: Alex Rocha <alexr1@vmware.com>
moleske added a commit to cloudfoundry/capi-release that referenced this issue Mar 2, 2022
cloudfoundry/cloud_controller_ng#2619

Co-authored-by: Alex Rocha <alexr1@vmware.com>
Co-authored-by: Michael Oleske <moleske@pivotal.io>
sethboyles added a commit to cloudfoundry/capi-dockerfiles that referenced this issue Mar 3, 2022
* cloudfoundry/cloud_controller_ng#2619

Co-authored-by: Michael Oleske <moleske@pivotal.io>
Co-authored-by: Seth Boyles <sboyles@pivotal.io>
sethboyles added a commit that referenced this issue Mar 3, 2022
[#2619]

Co-authored-by: Seth Boyles <sboyles@pivotal.io>
Co-authored-by: Alex Rocha <alexr1@vmware.com>
sethboyles pushed a commit to cloudfoundry/capi-release that referenced this issue Mar 3, 2022
cloudfoundry/cloud_controller_ng#2619

Co-authored-by: Michael Oleske <moleske@pivotal.io>
Co-authored-by: Alex Rocha <alexr1@vmware.com>
@sethboyles
Copy link
Member

yjit available with config flag here: cloudfoundry/capi-release#270

will-gant pushed a commit to sap-contributions/cloud_controller_ng that referenced this issue Dec 16, 2022
[cloudfoundry#2619]

Co-authored-by: Seth Boyles <sboyles@pivotal.io>
Co-authored-by: Alex Rocha <alexr1@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance PoC Issue/PR that is part of a PoC to try out new things
Projects
Development

Successfully merging a pull request may close this issue.

3 participants