Re: pgbench transaction timestamps

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: pgbench transaction timestamps
Date: 2007-04-02 21:18:57
Message-ID: 200704022118.l32LIvA16108@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Your patch has been added to the PostgreSQL unapplied patches list at:

http://momjian.postgresql.org/cgi-bin/pgpatches

It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.

---------------------------------------------------------------------------

Greg Smith wrote:
> This patch changes the way pgbench outputs its latency log files so that
> every transaction gets a timestamp and notes which transaction type was
> executed. It's a one-line change that just dumps some additional
> information that was already sitting in that area of code. I also made a
> couple of documentation corrections and clarifications on some of the more
> confusing features of pgbench.
>
> It's straightforward to parse log files in this format to analyze what
> happened during the test at a higher level than was possible with the
> original format. You can find some rough sample code to convert this
> latency format into CVS files and then into graphs at
> http://www.westnet.com/~gsmith/content/postgresql/pgbench.htm which I'll
> be expanding on once I get all my little patches sent in here.
>
> If you recall the earlier version of this patch I submitted, it added a
> cleanup feature that did a vacuum and checkpoint after the test was
> finished and reported two TPS results. The idea was to quantify how much
> of a hit the eventual table maintenance required to clean up after the
> test would take. While those things do influence results and cause some
> of the run-to-run variation in TPS (checkpoints are particularly visible
> in the graphs), after further testing I concluded running a VACUUM VERBOSE
> and CHECKPOINT in a script afterwards and analyzing the results was more
> useful than integrating something into pgbench itself.
>
> --
> * Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
Content-Description:

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-04-02 21:19:58 Re: Is this portable?
Previous Message Alvaro Herrera 2007-04-02 21:16:37 Re: Questions about pid file creation code

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-04-02 21:27:30 Re: Current enums patch
Previous Message Bruce Momjian 2007-04-02 21:16:28 Re: [HACKERS] Full page writes improvement, code update