|
|
|
|
|
|
by byroot
1247 days ago
|
|
|
There might be a number of reasons why YJIT isn't effective in your application. The best way to know it to enable YJIT runtime statistics [0] to see whether YJIT is doing a lot of side exits and if so why. But it requires a bit of YJIT knowledge to interpret them. It's also entirely possible that your application isn't CPU bound in the first place, or that it's bottlenecked by things YJIT can't do anything about (e.g. GVL). That's close to impossible to guess what it might be without being able to instrument the application. [0] https://github.com/ruby/ruby/blob/df6b72b8ff7af16a56fa48f3b4... |
|
|