High-volume writes - what is the max throughput possible - Mailing list pgsql-performance

From Geervan Hayatnagarkar
Subject High-volume writes - what is the max throughput possible
Date
Msg-id CAP=n9p2i7HQzfs0XkP23RLEjuTLREVJU+12HxQURceJhSFTA6g@mail.gmail.com
Whole thread Raw
Responses Re: High-volume writes - what is the max throughput possible  (Frits Jalvingh <jal@etc.to>)
List pgsql-performance
Hi,

We are trying to find maximum throughput in terms of transactions per second (or simultaneous read+write SQL operations per second) for a use case that does one ACID transaction (consisting of tens of reads and tens of updates/ inserts) per incoming stream element on a high-volume high-velocity stream of data.

Our load test showed us that PostgreSQL version 11/12 could support upto 10,000 to 11,000 such ACID transactions per second = 55K read SQL operations per second along with simultaneous 77 K write SQL operations per second (= total 132 K total read+write SQL operations per second) 

The underlying hardware limit is much more. But is this the maximum PostgreSQL can support? If not what are the server tuning parameters we should consider for this scale of throughput ? 

Thanks,
Arti

pgsql-performance by date:

Previous
From: Yoan SULTAN
Date:
Subject: Re: Odd (slow) plan choice with min/max
Next
From: Nikhil Shetty
Date:
Subject: Re: How do we hint a query to use index in postgre