This document discusses enhancing Ruby code performance using multithreading, covering key concepts like processes vs. threads and concurrency vs. parallelism. It highlights the limitations of Ruby's standard version in achieving true parallelism due to the global interpreter lock and explains the importance of handling race conditions and using mutexes for thread safety. The author, a software engineer and technical writer, shares insights on the practical applications of multithreading in Ruby development.

1. How to make your
Ruby code faster
with Multithreading
Sun-Li Beatteay

2. About Me
● Software Engineer @
DigitalOcean
● Technical Writer:
@SunnyB on Medium
● GitHub: sunny-b
● Twitter: @SunnyPaxos

3. Key Takeaways
1. Processes vs. Threads
2. Concurrency vs. Parallelism
3. How to use multithreading to speed up your code
a. Race Conditions
b. Mutex

4. Processes vs. Threads

5. Processes
● Each process is a running program (web
browser, Slack, Ruby/Bash script, etc.)
● Each CPU can run one process at a time
○ A CPU core can have more than one
process, but it will context switch
between them.
● `top`

6. Threads
● Each process has one Main
thread
● Share memory (same heap)
● Separate call stacks

7. Why is multithreading useful?

8. Concurrency vs. Parallelism

9. Parallelism
Tasks are completed in
parallel without pausing
or switching.

10. Concurrency
● Tasks overlap, but
don’t necessarily run
in parallel.
● Concurrency is not
the same as
parallelism.

11. Concurrency in Ruby
● Standard version of Ruby (MRI)
can’t achieve parallelism when
multithreading.
● Global Interpreter Lock prevents
threads from executing in
parallel.

12. “Not real threads”

13. Examples

14. Threads are Asynchronous

15. Race Conditions

16. Mutex
● Prevents multiple threads from accessing the
same shared resource at the same time
● Ensures thread safety

17. Thank You!
● Medium: @SunnyB
● GitHub: sunny-b
● Twitter: @SunnyPaxos
● Email: sjbeatteay@gmail.com
● Personal: http://www.sunli.co