Looks like the publisher may have taken this series offline or changed its URL. Please contact support if you believe it should be working, the feed URL is invalid, or you have any other concerns about it.
با برنامه Player FM !
Fixing a Thread-Safety Bug with Nate Berkopec
Fetch error
Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on April 18, 2024 10:51 (
What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.
Manage episode 359828805 series 2552731
Can you tell if a Ruby gem is really thread-safe or not? And how do you fix a seemingly thread-safety issue that can be something else entirely?
We had no idea. So we asked Nate Berkopec to help us. Nate is an expert in Ruby performance.
The verdict: nuking all shared global mutable state in your Ruby code is a bad idea if you don't know what you're doing!
Listen to this episode to learn:
- How and why faker-ruby became thread-unsafe, especially for Puma users
- Questions to ask yourself when trying to debug thread-safety issues
- Shared global mutable state is not always the villain, and is not the source of all thread-safety issues
- Nate's "watch-out" list of things that can cause undesired behavior when running multi-threaded Ruby applications: Constants, Class Variables, and Rack Middleware.
Episode Notes
🔗 Full transcript and links
-----
A special thanks to Valentino Stoll, nfstern02, and Gregg P for sponsoring hexdevs!
Enjoy!
37 قسمت
Fetch error
Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on April 18, 2024 10:51 (
What now? This series will be checked again in the next day. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.
Manage episode 359828805 series 2552731
Can you tell if a Ruby gem is really thread-safe or not? And how do you fix a seemingly thread-safety issue that can be something else entirely?
We had no idea. So we asked Nate Berkopec to help us. Nate is an expert in Ruby performance.
The verdict: nuking all shared global mutable state in your Ruby code is a bad idea if you don't know what you're doing!
Listen to this episode to learn:
- How and why faker-ruby became thread-unsafe, especially for Puma users
- Questions to ask yourself when trying to debug thread-safety issues
- Shared global mutable state is not always the villain, and is not the source of all thread-safety issues
- Nate's "watch-out" list of things that can cause undesired behavior when running multi-threaded Ruby applications: Constants, Class Variables, and Rack Middleware.
Episode Notes
🔗 Full transcript and links
-----
A special thanks to Valentino Stoll, nfstern02, and Gregg P for sponsoring hexdevs!
Enjoy!
37 قسمت
همه قسمت ها
×
1 How to Beat Impostor Syndrome and Be a Happy Developer with Amor Muto 1:13:00


1 Unhappy as a Developer? How Not To Be Miserable with Dr. Randy Paterson 1:11:34

1 #20 Growing a micro-SaaS to $30k MRR with Preetam Nath and Sankalp Jonna from DelightChat 1:08:29
به Player FM خوش آمدید!
Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.