Replies: 1 comment 2 replies
-
Are you testing on Ruby 3.3? Looks like YJIT didn't start optimizing |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Starting in 5.49.0 sequel switched to using "defined?(yield) instead of block_given? internally for better performance on CRuby". I ran some recent benchmarks and found
block_given?
to be faster. I realized the reason was I had YJIT enabled, and in ruby/ruby#7202block_given?
became YJIT optimized. How do you think about YJIT with respect to performance optimizations like this? Should sequel change again to take advantage of YJIT, but end up being slower if you don't use it? Something else?Beta Was this translation helpful? Give feedback.
All reactions