public inbox for [email protected]  
help / color / mirror / Atom feed
From: Sam Stearns <[email protected]>
To: Holger Jakobs <[email protected]>
Cc: [email protected]
Subject: Re: Postgres Resource Sizing
Date: Wed, 15 Oct 2025 07:09:22 -0700
Message-ID: <CAN6TVjm_mU3m67ZbfzYPegG=fWDf+nS_3jvcRKkKPJyfiTUwjQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAN6TVjn5JkPcbxbuzrQC71uZ6xOBYZvq9f4WJh-Ka_aeZCtZ6A@mail.gmail.com>
	<[email protected]>

Thanks for the information, Holger!  This helps.  We have our VM's tuned
with help from PGTune.  I'll talk to our Linux team some more about the TPS.

Sam

On Tue, Oct 14, 2025 at 1:41 PM Holger Jakobs <[email protected]> wrote:

> Am 14. 10. 25 um 22: 32 schrieb Sam Stearns: Howdy, We have an Oracle
> database that is processing 500 transactions per second during peak hours.
>   We are migrating this to a Linux VM running Postgres 17. 6.   Is there
> anything out there that can give
> ZjQcmQRYFpfptBannerStart
> This Message Is From an External Sender
> This message came from outside your organization.
>
> ZjQcmQRYFpfptBannerEnd
> Am 14.10.25 um 22:32 schrieb Sam Stearns:
>
> Howdy,
>
> We have an Oracle database that is processing 500 transactions per second
> during peak hours.  We are migrating this to a Linux VM running Postgres
> 17.6.  Is there anything out there that can give recommendations on CPU /
> memory / shared_buffer sizing based on number of transactions per second
> rate?  PGTune doesn't seem to have number of transactions per second as an
> option.
>
> Thanks,
>
> Sam
>
> Hi Sam,
>
> The number of TPS you can achieve depends mainly on your (virtual)
> hardware, except that version 18 of PostgreSQL offers some improvements
> like asynchronous I/O.
>
> PGTune tells you how to configure your system to get the best results,
> depending on your type of workload (web, oltp, dw, ...) using the
> properties of your hardware.
>
> 500 TPS doesn't seem much, so that should be easily achievable with almost
> any system, but of course it depends on the size of the transactions. Have
> you had any issues?
>
> It's quite likely that 500 TPS can be performed without any tuning at all,
> although I wouldn't recommend that.
>
> Kind Regards
>
> Holger
>
>
>
> --
>
> Samuel Stearns
> Team Lead - Database
> c: 971 762 6879 | o: 971 762 6879 | DAT.com
>
> <https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link;
>
> --
>
> Holger Jakobs, Bergisch Gladbach, Germany
>


-- 

Samuel Stearns
Team Lead - Database
c: 971 762 6879 | o: 971 762 6879 | DAT.com

<https://www.dat.com/?utm_medium=email&utm_source=DAT_email_signature_link;


reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Postgres Resource Sizing
  In-Reply-To: <CAN6TVjm_mU3m67ZbfzYPegG=fWDf+nS_3jvcRKkKPJyfiTUwjQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox