| From: | Guillaume Cottenceau <gc(at)mnc(dot)ch> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgresql TPS Bottleneck |
| Date: | 2022-03-31 14:18:37 |
| Message-ID: | 87zgl64342.fsf@mnc.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
<wakandavision 'at' outlook.com> writes:
> Optimally I would like to fully use the CPU and get about 3-4 times
> more TPS (if even possible).
Disclaimer: I'm really not a pg performance expert.
I don't understand your hope to fully use the CPU; if your
scenario is disk-limited, which may very well be the case, then
of course you cannot fully use the CPU. With synchronous commits
and fsync, the system is probably spending time just waiting for
the disks to report the writes completion. Are iostat/vmstat
showing a lot of IO-wait?
Also, if you can live with a few lost transactions in case of
server crash, synchronous_commit=off is very ok and provides a
lot of performance gain.
--
Guillaume Cottenceau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mladen Gogala | 2022-03-31 14:44:57 | Re: HIGH IO and Less CPU utilization |
| Previous Message | wakandavision | 2022-03-31 11:50:34 | Postgresql TPS Bottleneck |