From: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
---|---|
To: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: AWS vs GCP storage |
Date: | 2022-02-22 21:38:48 |
Message-ID: | CANNMO+J-sNbmxY_-GO4b5H-wQgkf-L=rA6ODzHWm0bqbZGk2+w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Feb 22, 2022 at 12:27 PM Torsten Förtsch <tfoertsch123(at)gmail(dot)com>
wrote:
> Hi,
>
> I have a few databases with several TB-sized tables. We recently moved one
> of those databases from AWS EC2 to GCP. Today I ran VACUUM FREEZE on those
> tables and every time I saw our application freezing up (and throwing tons
> of errors) for a few minutes right after the message about the end of
> vacuum (duration: 30182257.392 ms statement: vacuum freeze verbose ...).
> We never saw anything like that on AWS.
>
> The database is 9.6. At the moment I have no details about the storage
> configuration on GCP. The machine was set up by another department.
>
> Any suggestions on why that is happening and how to prevent it would be
> appreciated.
>
The first thing to check is that you're using SSD PDs, not regular PDs.
Second: GCP has 2 rules for disk IO throttling (independent for regular PDs
and SSD PDs): based on disk size, and based on the number of vCPUs. You
need more vCPUs to get maximum disk IO, which may be counter-intuitive. I
suggest checking out the docs and benchmarking the disks using fio:
- https://cloud.google.com/compute/docs/disks/performance
- https://cloud.google.com/compute/docs/disks/benchmarking-pd-performance
From | Date | Subject | |
---|---|---|---|
Next Message | Radu Radutiu | 2022-02-23 13:44:24 | Plan regression from 12 to 13 |
Previous Message | Adrian Klaver | 2022-02-22 20:50:04 | Re: AWS vs GCP storage |