# Unusually high CPU usage

**URL:** https://meta.discourse.org/t/unusually-high-cpu-usage/394651
**Category:** Self-hosting
**Created:** [January 29, 2026, 1:27pm UTC](https://meta.discourse.org/t/unusually-high-cpu-usage/394651 "2026-01-29T13:27:05Z")
**Posts on this page:** 1
**Showing post:** 24

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [February 7, 2026, 2:04pm UTC](https://meta.discourse.org/t/unusually-high-cpu-usage/394651/24 "2026-02-07T14:04:50Z")

</div>

> [@pfaffman](#):
>
> Have you tried tweaking the postgres memory settings?

This feels like a good line of questioning to me: you might have lots of RAM, but postgres is configured to use it in certain ways, and might be making life hard for itself.

I don’t like that there are two UPDATE queries which look identical - that looks like it could be a scheduled task which took so long a second one got scheduled subsequently. It will be adding load in a situation where things are already not running well.

But I don’t know about how to do those tweaks.

---

_[View the full topic](https://meta.discourse.org/t/unusually-high-cpu-usage/394651)._