Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement) - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)
Date
Msg-id alpine.DEB.2.02.1306011053070.12964@localhost6.localdomain6
Whole thread Raw
In response to Re: [PATCH] pgbench --throttle (submission 6)  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)
List pgsql-hackers
New submission for the next commit fest.

This new version also reports the average lag time, i.e. the delay between 
scheduled and actual transaction start times. This may help detect whether 
things went smothly, or if at some time some delay was introduced because 
of the load and some catchup was done afterwards.

Question 1: should it report the maximum lang encountered?

Question 2: the next step would be to have the current lag shown under 
option --progress, but that would mean having a combined --throttle 
--progress patch submission, or maybe dependencies between patches.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Optimising Foreign Key checks
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Combo xids