In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#1

Post by chmaynard » Sun, Dec 15, 2024, 11:46 AM UTC

In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape
jpcamara.com

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#2

Post by adenta » Sun, Dec 15, 2024, 2:00 PM UTC

This was a great talk.

The Falcon web server scares me. I wish Puma had better support for web sockets/fibers.

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#3

Post by Alifatisk » Sun, Dec 15, 2024, 2:56 PM UTC

Very interesting talk, I remember trying to setup Falcon for a simple app once but the docs was lacking and I didn't get it to work, but this was years ago. It seem to have matured a lot since then.

I also remember the Parallel gem being higher performing than Ractors, is that still the case? Does anyone know?

There is also iodine, I kinda wish it got covered, I am very curious about it. https://github.com/boazsegev/iodine?tab=readme-ov-file#iodin...

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#4

Post by Alifatisk » Sun, Dec 15, 2024, 2:56 PM UTC

adenta wrote: post #2

This was a great talk. The Falcon web server scares me. I wish Puma had better support for web sockets/fibers.

Why does the Falcon server scare you?

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#5

Post by baggy_trough » Sun, Dec 15, 2024, 3:12 PM UTC

Alifatisk wrote: post #4

adenta wrote: post #2

This was a great talk. The Falcon web server scares me. I wish Puma had better support for web sockets/fibers.

Why does the Falcon server scare you?

It has a pre-release version number and a bus factor of approximately 1. It's tempting though.

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#6

Post by adenta » Sun, Dec 15, 2024, 3:49 PM UTC

baggy_trough wrote: post #5

Alifatisk wrote: post #4

Earlier quoted context omitted.

Why does the Falcon server scare you?

It has a pre-release version number and a bus factor of approximately 1. It's tempting though.

Yeah, Puma just seems more stable, and works out of the box with Kamal.

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#7

Post by adenta » Sun, Dec 15, 2024, 3:51 PM UTC

Alifatisk wrote: post #3

Very interesting talk, I remember trying to setup Falcon for a simple app once but the docs was lacking and I didn't get it to work, but this was years ago. It seem to have matured a lot since then. I also remember the Parallel gem being higher performing than Ractors, is that still the case? Does anyone know? There is also iodine, I kinda wish it got covered, I am very curious about it. https://github.com/boazsegev/…

I wish it was easy to use puma for almost everything, and then iodine/falcon for web sockets. Haven’t figured out a sensible solution yet.

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#8

Post by davidw » Sun, Dec 15, 2024, 6:23 PM UTC

I am not much of a video guy. Any kind of tl;dr?

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#9

Post by ksec » Sun, Dec 15, 2024, 6:28 PM UTC

adenta wrote: post #6

baggy_trough wrote: post #5

Earlier quoted context omitted.

It has a pre-release version number and a bus factor of approximately 1. It's tempting though.

Yeah, Puma just seems more stable, and works out of the box with Kamal.

And I am not aware of any heavy production use of Falcon with Rails. But in any case it already proves the async potential.

Re: In-Depth Ruby Concurrency: Navigating the Ruby Concurrency Landscape

#10

Post by Asmod4n » Sun, Dec 15, 2024, 6:28 PM UTC

davidw wrote: post #8

I am not much of a video guy. Any kind of tl;dr?

it just listed the ways you can handle concurrency and parallelism in ruby 3 and what they each do.

Aka Threads which are backed by OS threads but are limited by the GIL when it comes to parallelism. Fibers which are green threads aka windows 3 style concurrency. Forking Processes. and Ractor which is backed by a thread pool and offers real parallelism.