Joshua Young

ractor-shim/lib/ractor/shim.rb at 69d4d568fdac3f212de3e7d7c3133f31564dc4ec · eregon/ractor-shim A shim to define Ractor by using Thread, if not already defined - eregon/ractor-shim

Ah it has `#<<`, but hasn't aliased it to `#send`: github.com/eregon/racto...

Also, probably doesn't matter, but it's the other way around in CRuby i.e., `#<<` is the alias.

Has ractor-shim implemented `Ractor::Port#send`? That could be why if not. Ref: docs.ruby-lang.org/en/master/Ra...

github.com/joshuay03/at...

I don't have an answer, but I'm figuring that out myself with what I'm building (not ready to share yet). There's a point where the copying/moving/freezing (i.e., message passing) overhead might outweigh the parallelisation benefits. The answer will vary by the payload and the type of work.

Yes! I missed that. Clearly my Ractor coverage is lacking... @jhawthorn.com has already sent a fix: github.com/joshuay03/at.... I'll get that merged and released soon.

2. The thing that clicked for me was when @jhawthorn.com referred to a ractor as a no-GVL block at Rails World. Rather than chucking a whole Rails app in there, you could find CPU intensive code paths that would choke the GVL, and delegate them to a ractor or few. Think complex parsing of strings.

1. Could you clarify? I'm not aware of Ractors needing a C extension to work. Main limitation: C extension gems must mark themselves Ractor-safe. Shareable requirement on init/send exists, plus new semantics like move (may not last: bsky.app/profile/byro...). Docs: docs.ruby-lang.org/en/master/ra...

GitHub - joshuay03/ractor-pool: A thread-safe, lock-free pool of Ractor workers with a coordinator pattern for distributing work A thread-safe, lock-free pool of Ractor workers with a coordinator pattern for distributing work - joshuay03/ractor-pool

Announcing RactorPool: github.com/joshuay03/ra...

Extracted from a project I'm building with Ractors. Currently requires Ruby 3.5 (3.5.0.dev). Goal is to have it stable for Ruby 4.0, when Ractors will be less experimental 🤞🏽

Ah that’s unfortunate, that does seem like a tricky edge case… Being able to move in my case seems to be quite a bit more performant than both deeply copying (not surprising), and making shareable and duping just the objects I need to mutate in the receiver. Although, I haven’t properly benchmarked.

Fix segfault when moving nested objects between ractors during GC by joshuay03 · Pull Request #14947 · ruby/ruby Fixes a segmentation fault when moving nested objects between ractors with GC stress enabled and YJIT. The issue appears to be a timing problem in the ractor move process. When moving objects, move...

I'm building something with Ractors and found a bug. Tried my best™️ to fix it: github.com/ruby/ruby/pu...

Side note: Might just be me, but as a non-frequent contributor, building ruby/ruby and running tests seems to be much more convenient and efficient than it was a couple years ago.

Time for a holiday?

#railsworld | 🍯 Joshua Young Attended the third edition of Rails World earlier this month along with Jason and Julián, back in Amsterdam once again! A big thank you to Buildkite for sponsoring the three of us to attend this year....

September flew by pretty quickly… I kicked it off by attending #RailsWorld!

www.linkedin.com/posts/joshua...

Was it the colonoscopy room?

I’ve added support for distributed deployments: github.com/joshuay03/di...

Couple of ideas to follow up on:
- Profile dashboard
- Profile comparisons

This is from a Datadog APM notebook I used to monitor the impact.

Haha yep, I have to remind myself from time to time as well.

Yes, at the very end of a before_fork—after doing any necessary closing of connections, shutting down threads, etc.

Satisfying memory and CPU improvements after enabling Puma preloading + Process.warmup on one of Buildkite's services (our agent shard). Just rolled this out to all services - keen to see the broader impact!

It probably hasn’t been released yet. I would first check if the change has been back-ported to the `8-0-stable` branch, and then whether it was actually included in a release. If not, and it’s already on the branch, it’ll probably be released in a 8.0.x at some point, else 8.1.x.

What a run! Hope you enjoy some well deserved time off!

Allow sending SIGTERM to workers on timeout by schneems · Pull Request #157 · zombocom/rack-timeout When rack-timeout fires then it can put an application in a &quot;bad&quot; state. This is due to https://www.schneems.com/2017/02/21/the-oldest-bug-in-ruby-why-racktimeout-might-hose-your-server/....

> I believe `Rack::Timeout` does trigger a full process shutdown after killing a thread.

You need to opt in by enabling `term_on_timeout` (github.com/zombocom/rac...).

TIL 👀 Thanks!

Yes, just 3-12 bytes:
- github.com/puma/puma/bl...
- github.com/puma/puma/bl...

Good point, mmap + polling + small messages is probably less efficient than using pipes in this case. I'm still going to give it a go to scratch that itch 😊

I’m curious how Puma would perform with mmap instead of pipes, which it relies on heavily for IPC in cluster mode: github.com/puma/puma/bl....

I wrote (or rewrote) some gems to get better at Ruby C extensions and learn about these topics (CAS and mmap):
- github.com/joshuay03/at...
- github.com/joshuay03/mm...

I'm curious about this too. With YJIT in maintenance mode, bug fixes, UX improvements, etc., are probably welcome (a colleague recently found and fixed one). But with ZJIT being greenfield WIP, I'm not so sure. Completely understandable if that's the case though.

Young* 🙂

#rubykaigi | 🍯 Joshua Young Ruby friends, old and new, at #RubyKaigi 2025—another amazing edition of the largest and most prestigious Ruby conference. I love this community and this event, and hope to be back every year ❤️ Hug...

Had a blast at #RubyKaigi 2025!

www.linkedin.com/posts/joshua...

Great talk! Though my favorite is still the one you gave at RailsConf 2022.

As a noob OSS contributor and maintainer, I’ve learned a lot from your talks about the "duties" and "responsibilities" of both sides in OSS interactions—I’m trying to apply those principles in my own work as well.

#RubyKaigi late night with #RubyFriends !