Re: Running concurrent txns and measuring the timings in Postgres

On 7/24/19 12:22 PM, Souvik Bhattacherjee 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.

The duplicate elimination is being handled by ON CONFLICT or some custom
process in the code generating the transactions?

If the transactions are being created from a single app/script could you
not just use 'timing' to mark the beginning of the transactions and the
end and record that somewhere(db table and/or file)?

>
> On Wed, Jul 24, 2019 at 1:58 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> On 7/24/19 9:54 AM, Souvik Bhattacherjee wrote:
> > Hi,
> >
> > Is there a standard procedure to execute two or more concurrent
> txns at
> > the same time? I understand that if we want to run concurrent
> txns, we
> > need to execute them from different psql sessions. But how do we
> make
> > sure that they begin execution almost at the same time.
>
> Well different sessions be they psql or some other client. That
> would be
> the difficulty, determining what is submitting the transaction.
>
> >
> > Also, I'm interested in measuring the time taken across all
> executing
> > txns, i.e. the time from the start of the earliest txns till the
> end of
> > the last txn.
>
> It would help to know what problem you are trying to solve?
>
> >
> > Best,
> > -SB
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com