wok
yjit
wok | yjit | |
---|---|---|
1 | 9 | |
24 | 631 | |
- | 1.4% | |
0.0 | 4.7 | |
almost 2 years ago | 7 months ago | |
Ruby | Ruby | |
ISC License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wok
-
Wok 0.3 released
A function pointers can be seen here: https://github.com/wolfgangj/wok/blob/master/tests/ok/ok-1.wok
yjit
-
Install Ruby 3.2.0 with YJIT
Ruby 3.2.0 is here and it offers some nice additions to the language. One of the most exciting new things is the addition of a compiler, YJIT. YJIT was created by the folks from Shopify and has been producion tested for a while, so it is safe to use in your environment. Some benchmarks show the difference in speed compared to Ruby without YJIT. I'll put some links if you want to know more: https://speed.yjit.org/ https://www.solnic.dev/p/benchmarking-ruby-32-with-yjit
-
Ruby 3.1.0 Preview 1 released with new experimental JIT
> I’m curious how the impact affects development, deployment, etc.
YJIT is pretty much transparent in production, if not it's likely a bug.
When we tried MJIT in production to compare it against YJIT, it causes lots of request timeouts on deploy, because the JIT warmup would take 10 to 20 minutes and it's much slower during that phase.
But YJIT warms ups extremely fast and with a much lower overhead, it's seemless on deploy.
The only thing you may need to tweak is `--yjit-exec-mem-size`, it defaults to `--yjit-exec-mem-size=256` (MB) which is not quite enough for larger apps.
As for development, it would work, but with code reloading enabled, you'd likely exhaust the executable memory allocation pretty fast, because for now YJIT doesn't GC generated code [0]. It will come soon, hopefully before the 3.1.0 release, but that's one of the reason why it's not enabled by default.
[0] https://github.com/Shopify/yjit/issues/87
-
YJIT: Building a New JIT Compiler for CRuby
Just want to temper expectations because YJIT is still new. But if you run into crashes or bugs, please open an issue with as much detail as you can: https://github.com/Shopify/yjit
-
Sorbet Compiler: An experimental, ahead-of-time compiler for Ruby
You raised a point that the compiler only does a subset. That's actually what I would expect from a new project. I don't expect a full implementation to start. It takes time for a compiler to be mature enough to be general purpose. Here is another Ruby compiler in its infancy: https://github.com/Shopify/yjit.
-
Ruby and Rails never had anything like Shopify
We already collaborate extensively with GitHub around Rails and Ruby. Our respective Ruby and Rails infra teams hold regular meetings, and they already contributed substantial patches to YJIT, e.g. https://github.com/Shopify/yjit/pulls/jhawthorn. Also things like https://bugs.ruby-lang.org/issues/17763 are a collaboration.
-
YJIT: Building a New JIT Compiler Inside CRuby
Yes. I put some suggestions here. I realize that not all of them are practical, but refactoring specific hot methods could make a difference.
What are some alternatives?
okami - okami is an application development platform
Ruby on Rails - Ruby on Rails
ruby - The Ruby Programming Language
vox - Vox language compiler. AOT / JIT / Linker. Zero dependencies
Opal - Ruby ♥︎ JavaScript
rhizome - A JIT for Ruby, implemented in pure Ruby
natalie - a work-in-progress Ruby compiler, written in Ruby and C++
crystal - The Crystal Programming Language
typeprof - An experimental type-level Ruby interpreter for testing and understanding Ruby code
error_highlight - The gem enhances Exception#message by adding a short explanation where the exception is raised
CodeBehind Framework - CodeBehind library is a modern backend framework. This library is a programming model based on the MVC structure, which provides the possibility of creating dynamic aspx files in .NET Core and has high serverside independence.