Re: Running concurrent txns and measuring the timings in Postgres - Mailing list pgsql-general

From Rob Sargent
Subject Re: Running concurrent txns and measuring the timings in Postgres
Date
Msg-id 9FDB31EE-CEC5-4B19-B311-E96AC7139706@gmail.com
Whole thread Raw
In response to Re: Running concurrent txns and measuring the timings in Postgres  (Souvik Bhattacherjee <kivuosb@gmail.com>)
List pgsql-general

On Jul 24, 2019, at 1:22 PM, Souvik Bhattacherjee <kivuosb@gmail.com> wrote:

> It would help to know what problem you are trying to solve?

Multiple txns are inserting tuples into a table concurrently. Wanted to measure
the total time taken to complete the insertion process. Some txns overlap with
others on the tuples they insert. Duplicate tuples are not inserted.
Start both/all clients at approximately the same time, each firing a transaction at some believable interval. (Or separate threads with separate db connections.)  This should generate the concurrency load I think you’re looking for. You can easily time the iteration; actual details on server side would likely involve turning on maximum logging, with client identifier, and analyzing the logs.

pgsql-general by date:

Previous
From: Jatinder Sandhu
Date:
Subject: Re: partition table slow planning
Next
From: Adrian Klaver
Date:
Subject: Re: Running concurrent txns and measuring the timings in Postgres