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
Molinillo test suite order of magnitude slower than MRI #1415
Comments
Thanks very much for the report. Passing is great. Cold code (which is often specs) can be a bit slower than MRI on startup, but we will investigate what is going on here. |
Same thing for Addressable:
(Then there's the bundler issue adding another 4-5 minutes where ruby does it in ~4 seconds 😄) |
@dentarg Thanks for the report. The 4 seconds for For the specs:
That's a very long time to load, there is probably something going wrong there, we should investigate. |
Yes, around 1m instead of 5m: https://github.com/dentarg/addressable/runs/434731081?check_suite_focus=true |
|
@dentarg Thank you for trying with GitHub Actions and We should still take a look at loading time and why those tests are much slower on TruffleRuby. |
I just found this issue while trying to add support for Truffleruby in Rubocop (rubocop/rubocop#8602). |
Rubocop tests suit running with the Github action for |
@jaimerave I've opened a new issue for this: #2081 |
@segiddins on my machine now it runs in 40 sec, could you retest it, please?
|
Latest update:
|
@gogainda Thanks for the update, that looks pretty close to CRuby, so I think we can close this (most likely MultiTier by default helps). |
Steps to reproduce:
Running the specs takes ~5 seconds on MRI 2.5.1 on my machine, whereas with truffleruby it took 4.5 minutes. (But they all pass 🎆)
The text was updated successfully, but these errors were encountered: