# Discourse under heavy loads

**URL:** <https://meta.discourse.org/t/discourse-under-heavy-loads/30444>\
**Category:** Product Support\
**Created:** [6월 25, 2015, 6:48오전 UTC](https://meta.discourse.org/t/discourse-under-heavy-loads/30444 "2015-06-25T06:48:30Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [6월 26, 2015, 12:40오전 UTC](https://meta.discourse.org/t/discourse-under-heavy-loads/30444/5 "2015-06-26T00:40:01Z")

</div>

> [@michaeld](#):
>
> Discourse 1.0 with Ruby 2.1 so things might have gotten a bit better in the meanwhile

Also **very** important note, this anecdote is from a non-docker based install. Our docker based install is finely tuned and optimised. I would strongly suggest following @codinghorror’s advice in the preceding post.

---

_[View the full topic](https://meta.discourse.org/t/discourse-under-heavy-loads/30444)._