# How to optimize postgres and the discourse DB

**URL:** <https://meta.discourse.org/t/how-to-optimize-postgres-and-the-discourse-db/338275>\
**Category:** Product Support\
**Tags:** postgres\
**Created:** [November 25, 2024, 4:31pm UTC](https://meta.discourse.org/t/how-to-optimize-postgres-and-the-discourse-db/338275 "2024-11-25T16:31:49Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [December 9, 2024, 11:53am UTC](https://meta.discourse.org/t/how-to-optimize-postgres-and-the-discourse-db/338275/12 "2024-12-09T11:53:53Z")

</div>

Is small sidestep allowed? Are unicorns similar thing than workers of PHP? Some document tried explain that unicorns are actually HTTP-servers with own workers delivering requests to Ruby, and that’s why it is totally different. But both handles http-reguests allowing more concurrent requests and therefore more PHP-workers and more unicorns need more RAM — and for me those two are pretty much same.

Right or horrible wrong? I would like to understand the principle now, because I know why, when and how to adjust PHP-workers, but unicorns are just mystical and magical creatures for me.

---

_[View the full topic](https://meta.discourse.org/t/how-to-optimize-postgres-and-the-discourse-db/338275)._