# Getting Discourse running on JRuby

**URL:** <https://meta.discourse.org/t/getting-discourse-running-on-jruby/81273>\
**Category:** Development\
**Created:** [February 23, 2018, 12:14am UTC](https://meta.discourse.org/t/getting-discourse-running-on-jruby/81273 "2018-02-23T00:14:59Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![headius](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/headius/32/120277_2.png) [@headius](https://meta.discourse.org/u/headius)\
**Post date:** [February 26, 2018, 3:00pm UTC](https://meta.discourse.org/t/getting-discourse-running-on-jruby/81273/11 "2018-02-26T15:00:16Z")

</div>

That certainly isn’t my goal! JRuby would always be an alternative, and in some cases it may be a better choice than MRI for larger deployments. A single JRuby instance can handle an entire server load, maxing out all cores. If you are getting to the point of running 3 or 4 or 5 MRI instances, there may be a good case to try JRuby.

We also usually perform better, but that may take some tweaking early on.

---

_[View the full topic](https://meta.discourse.org/t/getting-discourse-running-on-jruby/81273)._