Fixing A Thread-Safety Bug With Nate Berkopec Hexdevs podcast

内容由hexdevs提供。所有播客内容（包括剧集、图形和播客描述）均由 hexdevs 或其播客平台合作伙伴直接上传和提供。如果您认为有人在未经您许可的情况下使用您的受版权保护的作品，您可以按照此处概述的流程进行操作https://zh.player.fm/legal。

hexdevs »
Fixing a Thread-Safety Bug with Nate Berkopec

2+ y ago 45:38

MP3•单集首页

已归档的系列专辑 ("不活跃的收取点" status)

When? This feed was archived on July 18, 2025 14:09 (5M ago). Last successful fetch was on April 18, 2024 10:51 (1+ y ago)

Why? 不活跃的收取点 status. 我们的伺服器已尝试了一段时间，但仍然无法截取有效的播客收取点

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

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!

35集单集