One long transaction or multiple short transactions? - Mailing list pgsql-performance

From Carlo
Subject One long transaction or multiple short transactions?
Date
Msg-id 003d01d0ffe4$9ae8f890$d0bae9b0$@stonebanks.ca
Whole thread Raw
Responses Re: One long transaction or multiple short transactions?
List pgsql-performance

We have a system which is constantly importing flat file data feeds into normalized tables in a DB warehouse over 10-20 connections. Each data feed row results in a single transaction of multiple single row writes to multiple normalized tables.

 

The more columns in the feed row, the more write operations, longer the transaction.

 

Operators are noticing that splitting a single feed of say – 100 columns – into two consecutive feeds of 50 columns improves performance dramatically. I am wondering whether the multi-threaded and very busy import environment causes non-linear performance degradation for longer transactions. Would the operators be advised to rewrite the feeds to result in more smaller transactions rather than fewer, longer ones?

 

Carlo

pgsql-performance by date:

Previous
From: Igor Neyman
Date:
Subject: Re: shared-buffers set to 24GB but the RAM only use 4-5 GB average
Next
From: FattahRozzaq
Date:
Subject: Re: shared-buffers set to 24GB but the RAM only use 4-5 GB average