Transaction commits VS Transaction commits (with parallel) VS querymean time - Mailing list pgsql-hackers

From Haribabu Kommi
Subject Transaction commits VS Transaction commits (with parallel) VS querymean time
Date
Msg-id CAJrrPGc9=jKXuScvNyQ+VNhO0FZk7LLAShAJRyZjnedd2D61EQ@mail.gmail.com
Whole thread Raw
Responses Re: Transaction commits VS Transaction commits (with parallel) VSquery mean time  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
Hi Hackers,

Does increase in Transaction commits per second means good query performance?
Why I asked this question is, many monitoring tools display that number of transactions
per second in the dashboard (including pgadmin).

During the testing of bunch of queries with different set of configurations, I observed that
TPS of some particular configuration has increased compared to default server configuration, but the overall query execution performance is decreased after comparing all queries run time. 

This is because of larger xact_commit value than default configuration. With the changed server configuration, that leads to generate more parallel workers and every parallel worker operation is treated as an extra commit, because of this reason, the total number of commits increased, but the overall query performance is decreased.

Is there any relation of transaction commits to performance? 
 
Is there any specific reason to consider the parallel worker activity also as a transaction commit? Especially in my observation, if we didn't consider the parallel worker activity as separate commits, the test doesn't show an increase in transaction commits.

Suggestions?

Regards,
Haribabu Kommi
Fujitsu Australia

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: ToDo: show size of partitioned table
Next
From: Jose Luis Tallon
Date:
Subject: Re: phase out ossp-uuid?