# Discourse on Truffleruby

**URL:** <https://meta.discourse.org/t/discourse-on-truffleruby/169919>\
**Category:** Development\
**Created:** [November 12, 2020, 11:12am UTC](https://meta.discourse.org/t/discourse-on-truffleruby/169919 "2020-11-12T11:12:51Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![eregon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eregon/32/188324_2.png) [@eregon](https://meta.discourse.org/u/eregon)\
**Post date:** [February 10, 2023, 12:19pm UTC](https://meta.discourse.org/t/discourse-on-truffleruby/169919/12 "2023-02-10T12:19:47Z")

</div>

Brandon got Discourse running a year ago:  
[https://twitter.com/brandonfish/status/1486755128577253376](https://twitter.com/brandonfish/status/1486755128577253376)  
[https://twitter.com/brandonfish/status/1519726230936993792](https://twitter.com/brandonfish/status/1519726230936993792)

One issue IIRC was some gems rely on Hash being thread-safe, which we have a general solution for but is not merged/integrated yet in TruffleRuby. OTOH it’s very rarely correct to just use Hash concurrently, it often results in hiding concurrency bugs in harder-to-find ways. So it’s arguably better to just fix the gems relying on that, but that takes time.  
We need to benchmark performance, and for that to be meaningful/representative we should benchmark multi-threaded. That needs [A way to mark C extensions as thread-safe, so they can be executed in parallel · Issue #2136 · truffleruby/truffleruby · GitHub](https://github.com/oracle/truffleruby/issues/2136)

---

_[View the full topic](https://meta.discourse.org/t/discourse-on-truffleruby/169919)._