# Troubleshooting severe performance issues with latest Discourse?

**URL:** https://meta.discourse.org/t/troubleshooting-severe-performance-issues-with-latest-discourse/182995
**Category:** Self-hosting
**Created:** [March 12, 2021, 10:40am UTC](https://meta.discourse.org/t/troubleshooting-severe-performance-issues-with-latest-discourse/182995 "2021-03-12T10:40:20Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [March 31, 2021, 3:14pm UTC](https://meta.discourse.org/t/troubleshooting-severe-performance-issues-with-latest-discourse/182995/12 "2021-03-31T15:14:53Z")

</div>

There is definitely something wrong with your install; you should be getting much better performance with this hardware.

Try having postgres do an explicit vacuum. If you’re running the all-in-one container install:

```plaintext
# docker exec -it -u postgres app psql discourse
psql (13.1 (Debian 13.1-1.pgdg100+1))
Type "help" for help.

discourse=# VACUUM ANALYZE;
VACUUM

```

How many unicorn workers do you have set in your app.yml?

You can ask Discourse to set additional performance headers in responses with the following in your `env` section:

```plaintext
DISCOURSE_ENABLE_PERFORMANCE_HTTP_HEADERS: true

```

While you’re at it, you can enable miniprofiler by following [this post](https://meta.discourse.org/t/long-loading-times-for-user-summary-page-with-slow-database/131870/6).

---

_[View the full topic](https://meta.discourse.org/t/troubleshooting-severe-performance-issues-with-latest-discourse/182995)._