Re: Improving insert performance - Mailing list pgsql-performance

From Greg Sabino Mullane
Subject Re: Improving insert performance
Date
Msg-id CAKAnmmLdeAMr6BSXfqSt-psk_bCsGh=ksyUHRtM9A49DOqsifg@mail.gmail.com
Whole thread
In response to Improving insert performance  (Русинов Семен <mrpinkolik@gmail.com>)
Responses Re: Improving insert performance
List pgsql-performance
You can definitely do better than 35k rps. Setting the table as unlogged is a great start. Are you using prepared queries? Have you tried COPY? What is the size of the typical rows going in? Have you tried version 18?

By using small string values and COPY, I can easily get over 1 million rows per second on a single thread, on an underpowered and fairly busy laptop, to give you a rough idea of potential. Checking wait_events as Laurenz says is a great idea. I'd also do 10 inserts with log_statement='all' on so you can see exactly what the driver and application are really doing for those inserts. Play around with the thread sizes to find the best combo.

> transactional inserts: yes

This is worrisome - are you committing after every insert? That's gonna hurt performance.


Cheers,
Greg

pgsql-performance by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Significant performance issues with array_agg() + HashAggregate plans on Postgres 17
Next
From: Roland Müller
Date:
Subject: Re: Improving insert performance