# CPU 사용량이 비정상적으로 높음

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

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [2월 10, 2026, 3:41오후 UTC](https://meta.discourse.org/t/unusually-high-cpu-usage/394651/29 "2026-02-10T15:41:30Z")

</div>

여러 GB의 공간이 남아 있음에도 불구하고 공간 부족으로 인해 마이그레이션 중 복원/업그레이드가 실패한 사례가 몇 번 있었습니다 (예: [Restore fails due to disk space on migration because of 70M calendar events](https://meta.discourse.org/t/restore-fails-due-to-disk-space-on-migration/395584)).

백업 전에 vacuum을 실행하면 이 문제를 해결하는 데 도움이 될까요?

또한

> [@supermathie](#):
>
> pause sidekiq then `vacuum analyze full`

이것은

```
 discourse=# VACUUM FULL ANALYZE;

```

---

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