Home/ Questions/Q 8934533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T09:48:33+00:00

I have been reading about Ruby 1.9 Thread and I see that all ruby

  • 0

I have been reading about Ruby 1.9 Thread and I see that all ruby threads go through the Global Interpreter Lock (GIL for friends) and that concurrency is actually non-existant.

I have done a test (without any signals nor waiting) and the performance using threads doesn’t only not improve but the operations actually take more time than running them serially

My question is basically – Whats the point for these Threads if they are not concurrent? Is there any hope that they will be concurrent in the future?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    A lot of other Ruby interpreters (JRuby, Rubinius) don’t actually have GILs. Also, MRI 2.0 is going to do away with the GIL as well.

    Also, in a lot of cases (such as when waiting for IO) the interpreter does switch to another thread. So while it’s not technically multithreading (in the case of MRI/REE as of 1.9), it does get some of the benefits.

    • 0