# Temporal database resource consumption

**URL:** <https://community.temporal.io/t/temporal-database-resource-consumption/7753>\
**Category:** Community Support\
**Created:** [March 31, 2023, 12:22pm UTC](https://community.temporal.io/t/temporal-database-resource-consumption/7753 "2023-03-31T12:22:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnP](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/johnp/32/1965_2.png) [@JohnP](https://community.temporal.io/u/JohnP)\
**Post date:** [March 31, 2023, 12:22pm UTC](https://community.temporal.io/t/temporal-database-resource-consumption/7753/1 "2023-03-31T12:22:13Z")

</div>

Our Postgres (v13) database used by Temporal server is regularly exceeding 90% utilization of CPU. It is running in GCP SQL and has 16 vCPU and 104GB memory allocated which seems like a lot. Our system handles about two million workflows evenly throughout each day which doesn’t seem excessive. We feel it is slowing down throughput as the number of pending workflows keeps climbing and goes down only when there is a reduction in input.

Are there any configuration tips or recommendations for our database to more efficient operate or is this a normal allocation for it. Note that all application data are stored in other databases.

---

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [March 31, 2023, 9:02pm UTC](https://community.temporal.io/t/temporal-database-resource-consumption/7753/2 "2023-03-31T21:02:08Z")

</div>

What server version are you running?

If you have server metrics enabled can you check and share sync-match rate:

`sum(rate(poll_success_sync{}[1m])) / sum(rate(poll_success{}[1m]))`

---

<div class="post-metadata">

**Author:** ![JohnP](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/johnp/32/1965_2.png) [@JohnP](https://community.temporal.io/u/JohnP)\
**Post date:** [March 31, 2023, 11:37pm UTC](https://community.temporal.io/t/temporal-database-resource-consumption/7753/3 "2023-03-31T23:37:15Z")

</div>

> [@tihomir](#):
>
> What server version are you running?

We are running 1.13. We don’t have server metrics enabled.

---

<div class="post-metadata">

**Author:** ![JohnP](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/johnp/32/1965_2.png) [@JohnP](https://community.temporal.io/u/JohnP)\
**Post date:** [April 6, 2023, 9:05pm UTC](https://community.temporal.io/t/temporal-database-resource-consumption/7753/4 "2023-04-06T21:05:26Z")

</div>

@tihomir Is the server version the issue?

The Temporal Postgres database is using 16 CPUs and 104GB memory yet it near capacity.

In contrast, we have a separate Postgres database instance hosting 12 databases that uses 4 CPUs and 16 GB.