Skip to content

P
Postgres FD Implementation
Commit a887c486 authored by Itagaki Takahiro's avatar Itagaki Takahiro
Browse files
Options

Each worker thread will have its own log file in pgbench to avoid interleaved 

writes. The first worker still uses "pgbench_log.<pid>" for the name, but
additional workers use "pgbench_log.<pid>.<serial-number>" instead.

Reported by Greg Smith.
parent 1d34814a
Hide whitespace changes
Inline Side-by-side
Showing with 681 additions and 660 deletions
contrib/pgbench/pgbench.c
View file @ a887c486
...@@ -4,7 +4,7 @@ ...@@ -4,7 +4,7 @@
* A simple benchmark program for PostgreSQL * A simple benchmark program for PostgreSQL
* Originally written by Tatsuo Ishii and enhanced by many contributors. * Originally written by Tatsuo Ishii and enhanced by many contributors.
* *
* $PostgreSQL: pgsql/contrib/pgbench/pgbench.c,v 1.97 2010/02/26 02:00:32 momjian Exp $ * $PostgreSQL: pgsql/contrib/pgbench/pgbench.c,v 1.98 2010/03/23 01:29:22 itagaki Exp $
* Copyright (c) 2000-2010, PostgreSQL Global Development Group * Copyright (c) 2000-2010, PostgreSQL Global Development Group
* ALL RIGHTS RESERVED; * ALL RIGHTS RESERVED;
* *
...@@ -131,11 +131,9 @@ int fillfactor = 100; ...@@ -131,11 +131,9 @@ int fillfactor = 100;
#define ntellers 10 #define ntellers 10
#define naccounts 100000 #define naccounts 100000
FILE *LOGFILE = NULL;
bool use_log; /* log transaction latencies to a file */ bool use_log; /* log transaction latencies to a file */
bool is_connect; /* establish connection for each transaction */
int is_connect; /* establish connection for each transaction */ int main_pid; /* main process id used in log filename */
char *pghost = ""; char *pghost = "";
char *pgport = ""; char *pgport = "";
...@@ -183,6 +181,7 @@ typedef struct ...@@ -183,6 +181,7 @@ typedef struct
*/ */
typedef struct typedef struct
{ {
int tid; /* thread id */
pthread_t thread; /* thread handle */ pthread_t thread; /* thread handle */
CState *state; /* array of CState */ CState *state; /* array of CState */
int nstate; /* length of state[] */ int nstate; /* length of state[] */
...@@ -741,7 +740,7 @@ clientDone(CState *st, bool ok) ...@@ -741,7 +740,7 @@ clientDone(CState *st, bool ok)
/* return false iff client should be disconnected */ /* return false iff client should be disconnected */
static bool static bool
doCustom(CState *st, instr_time *conn_time) doCustom(CState *st, instr_time *conn_time, FILE *logfile)
{ {
PGresult *res; PGresult *res;
Command **commands; Command **commands;
...@@ -778,7 +777,7 @@ top: ...@@ -778,7 +777,7 @@ top:
/* /*
* transaction finished: record the time it took in the log * transaction finished: record the time it took in the log
*/ */
if (use_log && commands[st->state + 1] == NULL) if (logfile && commands[st->state + 1] == NULL)
{ {
instr_time now; instr_time now;
instr_time diff; instr_time diff;
...@@ -791,12 +790,12 @@ top: ...@@ -791,12 +790,12 @@ top:
#ifndef WIN32 #ifndef WIN32
/* This is more than we really ought to know about instr_time */ /* This is more than we really ought to know about instr_time */
fprintf(LOGFILE, "%d %d %.0f %d %ld %ld\n", fprintf(logfile, "%d %d %.0f %d %ld %ld\n",
st->id, st->cnt, usec, st->use_file, st->id, st->cnt, usec, st->use_file,
(long) now.tv_sec, (long) now.tv_usec); (long) now.tv_sec, (long) now.tv_usec);
#else #else
/* On Windows, instr_time doesn't provide a timestamp anyway */ /* On Windows, instr_time doesn't provide a timestamp anyway */
fprintf(LOGFILE, "%d %d %.0f %d 0 0\n", fprintf(logfile, "%d %d %.0f %d 0 0\n",
st->id, st->cnt, usec, st->use_file); st->id, st->cnt, usec, st->use_file);
#endif #endif
} }
...@@ -857,7 +856,7 @@ top: ...@@ -857,7 +856,7 @@ top:
INSTR_TIME_ACCUM_DIFF(*conn_time, end, start); INSTR_TIME_ACCUM_DIFF(*conn_time, end, start);
} }
if (use_log && st->state == 0) if (logfile && st->state == 0)
INSTR_TIME_SET_CURRENT(st->txn_begin); INSTR_TIME_SET_CURRENT(st->txn_begin);
if (commands[st->state]->type == SQL_COMMAND) if (commands[st->state]->type == SQL_COMMAND)
...@@ -1833,7 +1832,7 @@ main(int argc, char **argv) ...@@ -1833,7 +1832,7 @@ main(int argc, char **argv)
} }
break; break;
case 'C': case 'C':
is_connect = 1; is_connect = true;
break; break;
case 's': case 's':
scale_given = true; scale_given = true;
...@@ -1955,6 +1954,12 @@ main(int argc, char **argv) ...@@ -1955,6 +1954,12 @@ main(int argc, char **argv)
exit(1); exit(1);
} }
/*
* save main process id in the global variable because process id will be
* changed after fork.
*/
main_pid = (int) getpid();
if (nclients > 1) if (nclients > 1)
{ {
state = (CState *) realloc(state, sizeof(CState) * nclients); state = (CState *) realloc(state, sizeof(CState) * nclients);
...@@ -1980,20 +1985,6 @@ main(int argc, char **argv) ...@@ -1980,20 +1985,6 @@ main(int argc, char **argv)
} }
} }
if (use_log)
{
char logpath[64];
snprintf(logpath, 64, "pgbench_log.%d", (int) getpid());
LOGFILE = fopen(logpath, "w");
if (LOGFILE == NULL)
{
fprintf(stderr, "Couldn't open logfile \"%s\": %s", logpath, strerror(errno));
exit(1);
}
}
if (debug) if (debug)
{ {
if (duration <= 0) if (duration <= 0)
...@@ -2111,6 +2102,7 @@ main(int argc, char **argv) ...@@ -2111,6 +2102,7 @@ main(int argc, char **argv)
threads = (TState *) malloc(sizeof(TState) * nthreads); threads = (TState *) malloc(sizeof(TState) * nthreads);
for (i = 0; i < nthreads; i++) for (i = 0; i < nthreads; i++)
{ {
threads[i].tid = i;
threads[i].state = &state[nclients / nthreads * i]; threads[i].state = &state[nclients / nthreads * i];
threads[i].nstate = nclients / nthreads; threads[i].nstate = nclients / nthreads;
INSTR_TIME_SET_CURRENT(threads[i].start_time); INSTR_TIME_SET_CURRENT(threads[i].start_time);
...@@ -2159,8 +2151,6 @@ main(int argc, char **argv) ...@@ -2159,8 +2151,6 @@ main(int argc, char **argv)
INSTR_TIME_SET_CURRENT(total_time); INSTR_TIME_SET_CURRENT(total_time);
INSTR_TIME_SUBTRACT(total_time, start_time); INSTR_TIME_SUBTRACT(total_time, start_time);
printResults(ttype, total_xacts, nclients, nthreads, total_time, conn_total_time); printResults(ttype, total_xacts, nclients, nthreads, total_time, conn_total_time);
if (LOGFILE)
fclose(LOGFILE);
return 0; return 0;
} }
...@@ -2171,6 +2161,7 @@ threadRun(void *arg) ...@@ -2171,6 +2161,7 @@ threadRun(void *arg)
TState *thread = (TState *) arg; TState *thread = (TState *) arg;
CState *state = thread->state; CState *state = thread->state;
TResult *result; TResult *result;
FILE *logfile = NULL; /* per-thread log file */
instr_time start, instr_time start,
end; end;
int nstate = thread->nstate; int nstate = thread->nstate;
...@@ -2180,7 +2171,25 @@ threadRun(void *arg) ...@@ -2180,7 +2171,25 @@ threadRun(void *arg)
result = malloc(sizeof(TResult)); result = malloc(sizeof(TResult));
INSTR_TIME_SET_ZERO(result->conn_time); INSTR_TIME_SET_ZERO(result->conn_time);
if (is_connect == 0) /* open log file if requested */
if (use_log)
{
char logpath[64];
if (thread->tid == 0)
snprintf(logpath, sizeof(logpath), "pgbench_log.%d", main_pid);
else
snprintf(logpath, sizeof(logpath), "pgbench_log.%d.%d", main_pid, thread->tid);
logfile = fopen(logpath, "w");
if (logfile == NULL)
{
fprintf(stderr, "Couldn't open logfile \"%s\": %s", logpath, strerror(errno));
goto done;
}
}
if (!is_connect)
{ {
/* make connections to the database */ /* make connections to the database */
for (i = 0; i < nstate; i++) for (i = 0; i < nstate; i++)
...@@ -2202,7 +2211,7 @@ threadRun(void *arg) ...@@ -2202,7 +2211,7 @@ threadRun(void *arg)
int prev_ecnt = st->ecnt; int prev_ecnt = st->ecnt;
st->use_file = getrand(0, num_files - 1); st->use_file = getrand(0, num_files - 1);
if (!doCustom(st, &result->conn_time)) if (!doCustom(st, &result->conn_time, logfile))
remains--; /* I've aborted */ remains--; /* I've aborted */
if (st->ecnt > prev_ecnt && commands[st->state]->type == META_COMMAND) if (st->ecnt > prev_ecnt && commands[st->state]->type == META_COMMAND)
...@@ -2304,7 +2313,7 @@ threadRun(void *arg) ...@@ -2304,7 +2313,7 @@ threadRun(void *arg)
if (st->con && (FD_ISSET(PQsocket(st->con), &input_mask) if (st->con && (FD_ISSET(PQsocket(st->con), &input_mask)
|| commands[st->state]->type == META_COMMAND)) || commands[st->state]->type == META_COMMAND))
{ {
if (!doCustom(st, &result->conn_time)) if (!doCustom(st, &result->conn_time, logfile))
remains--; /* I've aborted */ remains--; /* I've aborted */
} }
...@@ -2326,6 +2335,8 @@ done: ...@@ -2326,6 +2335,8 @@ done:
result->xacts += state[i].cnt; result->xacts += state[i].cnt;
INSTR_TIME_SET_CURRENT(end); INSTR_TIME_SET_CURRENT(end);
INSTR_TIME_ACCUM_DIFF(result->conn_time, end, start); INSTR_TIME_ACCUM_DIFF(result->conn_time, end, start);
if (logfile)
fclose(logfile);
return result; return result;
} }
......
doc/src/sgml/pgbench.sgml
View file @ a887c486
<!-- $PostgreSQL: pgsql/doc/src/sgml/pgbench.sgml,v 1.12 2009/12/15 15:59:57 tgl Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/pgbench.sgml,v 1.13 2010/03/23 01:29:22 itagaki Exp $ -->
<sect1 id="pgbench"> <sect1 id="pgbench">
<title>pgbench</title> <title>pgbench</title>
<indexterm zone="pgbench"> <indexterm zone="pgbench">
<primary>pgbench</primary> <primary>pgbench</primary>
</indexterm> </indexterm>
<para> <para>
<application>pgbench</application> is a simple program for running benchmark <application>pgbench</application> is a simple program for running benchmark
tests on <productname>PostgreSQL</>. It runs the same sequence of SQL tests on <productname>PostgreSQL</>. It runs the same sequence of SQL
commands over and over, possibly in multiple concurrent database sessions, commands over and over, possibly in multiple concurrent database sessions,
and then calculates the average transaction rate (transactions per second). and then calculates the average transaction rate (transactions per second).
By default, <application>pgbench</application> tests a scenario that is By default, <application>pgbench</application> tests a scenario that is
loosely based on TPC-B, involving five <command>SELECT</>, loosely based on TPC-B, involving five <command>SELECT</>,
<command>UPDATE</>, and <command>INSERT</> commands per transaction. <command>UPDATE</>, and <command>INSERT</> commands per transaction.
However, it is easy to test other cases by writing your own transaction However, it is easy to test other cases by writing your own transaction
script files. script files.
</para> </para>
<para> <para>
Typical output from pgbench looks like: Typical output from pgbench looks like:
<programlisting> <programlisting>
transaction type: TPC-B (sort of) transaction type: TPC-B (sort of)
scaling factor: 10 scaling factor: 10
query mode: simple query mode: simple
number of clients: 10 number of clients: 10
number of threads: 1 number of threads: 1
number of transactions per client: 1000 number of transactions per client: 1000
number of transactions actually processed: 10000/10000 number of transactions actually processed: 10000/10000
tps = 85.184871 (including connections establishing) tps = 85.184871 (including connections establishing)
tps = 85.296346 (excluding connections establishing) tps = 85.296346 (excluding connections establishing)
</programlisting> </programlisting>
The first six lines report some of the most important parameter The first six lines report some of the most important parameter
settings. The next line reports the number of transactions completed settings. The next line reports the number of transactions completed
and intended (the latter being just the product of number of clients and intended (the latter being just the product of number of clients
and number of transactions per client); these will be equal unless the run and number of transactions per client); these will be equal unless the run
failed before completion. The last two lines report the TPS rate, failed before completion. The last two lines report the TPS rate,
figured with and without counting the time to start database sessions. figured with and without counting the time to start database sessions.
</para> </para>
<sect2> <sect2>
<title>Overview</title> <title>Overview</title>
<para> <para>
The default TPC-B-like transaction test requires specific tables to be The default TPC-B-like transaction test requires specific tables to be
set up beforehand. <application>pgbench</> should be invoked with set up beforehand. <application>pgbench</> should be invoked with
the <literal>-i</> (initialize) option to create and populate these the <literal>-i</> (initialize) option to create and populate these
tables. (When you are testing a custom script, you don't need this tables. (When you are testing a custom script, you don't need this
step, but will instead need to do whatever setup your test needs.) step, but will instead need to do whatever setup your test needs.)
Initialization looks like: Initialization looks like:
<programlisting> <programlisting>
pgbench -i <optional> <replaceable>other-options</> </optional> <replaceable>dbname</> pgbench -i <optional> <replaceable>other-options</> </optional> <replaceable>dbname</>
</programlisting> </programlisting>
where <replaceable>dbname</> is the name of the already-created where <replaceable>dbname</> is the name of the already-created
database to test in. (You may also need <literal>-h</>, database to test in. (You may also need <literal>-h</>,
<literal>-p</>, and/or <literal>-U</> options to specify how to <literal>-p</>, and/or <literal>-U</> options to specify how to
connect to the database server.) connect to the database server.)
</para> </para>
<caution> <caution>
<para> <para>
<literal>pgbench -i</> creates four tables <structname>pgbench_accounts</>, <literal>pgbench -i</> creates four tables <structname>pgbench_accounts</>,
<structname>pgbench_branches</>, <structname>pgbench_history</>, and <structname>pgbench_branches</>, <structname>pgbench_history</>, and
<structname>pgbench_tellers</>, <structname>pgbench_tellers</>,
destroying any existing tables of these names. destroying any existing tables of these names.
Be very careful to use another database if you have tables having these Be very careful to use another database if you have tables having these
names! names!
</para> </para>
</caution> </caution>
<para> <para>
At the default <quote>scale factor</> of 1, the tables initially At the default <quote>scale factor</> of 1, the tables initially
contain this many rows: contain this many rows:
</para> </para>
<programlisting> <programlisting>
table # of rows table # of rows
--------------------------------- ---------------------------------
pgbench_branches 1 pgbench_branches 1
pgbench_tellers 10 pgbench_tellers 10
pgbench_accounts 100000 pgbench_accounts 100000
pgbench_history 0 pgbench_history 0
</programlisting> </programlisting>
<para> <para>
You can (and, for most purposes, probably should) increase the number You can (and, for most purposes, probably should) increase the number
of rows by using the <literal>-s</> (scale factor) option. The of rows by using the <literal>-s</> (scale factor) option. The
<literal>-F</> (fillfactor) option might also be used at this point. <literal>-F</> (fillfactor) option might also be used at this point.
</para> </para>
<para> <para>
Once you have done the necessary setup, you can run your benchmark Once you have done the necessary setup, you can run your benchmark
with a command that doesn't include <literal>-i</>, that is with a command that doesn't include <literal>-i</>, that is
<programlisting> <programlisting>
pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</> pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
</programlisting> </programlisting>
In nearly all cases, you'll need some options to make a useful test. In nearly all cases, you'll need some options to make a useful test.
The most important options are <literal>-c</> (number of clients), The most important options are <literal>-c</> (number of clients),
<literal>-t</> (number of transactions), <literal>-T</> (time limit), <literal>-t</> (number of transactions), <literal>-T</> (time limit),
and <literal>-f</> (specify a custom script file). and <literal>-f</> (specify a custom script file).
See below for a full list. See below for a full list.
</para> </para>
<para> <para>
<xref linkend="pgbench-init-options"> shows options that are used <xref linkend="pgbench-init-options"> shows options that are used
during database initialization, while during database initialization, while
<xref linkend="pgbench-run-options"> shows options that are used <xref linkend="pgbench-run-options"> shows options that are used
while running benchmarks, and while running benchmarks, and
<xref linkend="pgbench-common-options"> shows options that are useful <xref linkend="pgbench-common-options"> shows options that are useful
in both cases. in both cases.
</para> </para>
<table id="pgbench-init-options"> <table id="pgbench-init-options">
<title><application>pgbench</application> initialization options</title> <title><application>pgbench</application> initialization options</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
<entry>Option</entry> <entry>Option</entry>
<entry>Description</entry> <entry>Description</entry>
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row> <row>
<entry><literal>-i</literal></entry> <entry><literal>-i</literal></entry>
<entry> <entry>
Required to invoke initialization mode. Required to invoke initialization mode.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-s</literal> <replaceable>scale_factor</></entry> <entry><literal>-s</literal> <replaceable>scale_factor</></entry>
<entry> <entry>
Multiply the number of rows generated by the scale factor. Multiply the number of rows generated by the scale factor.
For example, <literal>-s 100</> will create 10,000,000 rows For example, <literal>-s 100</> will create 10,000,000 rows
in the <structname>pgbench_accounts</> table. Default is 1. in the <structname>pgbench_accounts</> table. Default is 1.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-F</literal> <replaceable>fillfactor</></entry> <entry><literal>-F</literal> <replaceable>fillfactor</></entry>
<entry> <entry>
Create the <structname>pgbench_accounts</>, Create the <structname>pgbench_accounts</>,
<structname>pgbench_tellers</> and <structname>pgbench_tellers</> and
<structname>pgbench_branches</> tables with the given fillfactor. <structname>pgbench_branches</> tables with the given fillfactor.
Default is 100. Default is 100.
</entry> </entry>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>
<table id="pgbench-run-options"> <table id="pgbench-run-options">
<title><application>pgbench</application> benchmarking options</title> <title><application>pgbench</application> benchmarking options</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
<entry>Option</entry> <entry>Option</entry>
<entry>Description</entry> <entry>Description</entry>
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row> <row>
<entry><literal>-c</literal> <replaceable>clients</></entry> <entry><literal>-c</literal> <replaceable>clients</></entry>
<entry> <entry>
Number of clients simulated, that is, number of concurrent database Number of clients simulated, that is, number of concurrent database
sessions. Default is 1. sessions. Default is 1.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-j</literal> <replaceable>threads</></entry> <entry><literal>-j</literal> <replaceable>threads</></entry>
<entry> <entry>
Number of worker threads within <application>pgbench</application>. Number of worker threads within <application>pgbench</application>.
Using more than one thread can be helpful on multi-CPU machines. Using more than one thread can be helpful on multi-CPU machines.
The number of clients must be a multiple of the number of threads, The number of clients must be a multiple of the number of threads,
since each thread is given the same number of client sessions to manage. since each thread is given the same number of client sessions to manage.
Default is 1. Default is 1.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-t</literal> <replaceable>transactions</></entry> <entry><literal>-t</literal> <replaceable>transactions</></entry>
<entry> <entry>
Number of transactions each client runs. Default is 10. Number of transactions each client runs. Default is 10.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-T</literal> <replaceable>seconds</></entry> <entry><literal>-T</literal> <replaceable>seconds</></entry>
<entry> <entry>
Run the test for this many seconds, rather than a fixed number of Run the test for this many seconds, rather than a fixed number of
transactions per client. <literal>-t</literal> and transactions per client. <literal>-t</literal> and
<literal>-T</literal> are mutually exclusive. <literal>-T</literal> are mutually exclusive.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-M</literal> <replaceable>querymode</></entry> <entry><literal>-M</literal> <replaceable>querymode</></entry>
<entry> <entry>
Protocol to use for submitting queries to the server: Protocol to use for submitting queries to the server:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para><literal>simple</>: use simple query protocol.</para> <para><literal>simple</>: use simple query protocol.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>extended</>: use extended query protocol.</para> <para><literal>extended</>: use extended query protocol.</para>
</listitem> </listitem>
<listitem> <listitem>
<para><literal>prepared</>: use extended query protocol with prepared statements.</para> <para><literal>prepared</>: use extended query protocol with prepared statements.</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
The default is simple query protocol. (See <xref linkend="protocol"> The default is simple query protocol. (See <xref linkend="protocol">
for more information.) for more information.)
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-N</literal></entry> <entry><literal>-N</literal></entry>
<entry> <entry>
Do not update <structname>pgbench_tellers</> and Do not update <structname>pgbench_tellers</> and
<structname>pgbench_branches</>. <structname>pgbench_branches</>.
This will avoid update contention on these tables, but This will avoid update contention on these tables, but
it makes the test case even less like TPC-B. it makes the test case even less like TPC-B.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-S</literal></entry> <entry><literal>-S</literal></entry>
<entry> <entry>
Perform select-only transactions instead of TPC-B-like test. Perform select-only transactions instead of TPC-B-like test.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-f</literal> <replaceable>filename</></entry> <entry><literal>-f</literal> <replaceable>filename</></entry>
<entry> <entry>
Read transaction script from <replaceable>filename</>. Read transaction script from <replaceable>filename</>.
See below for details. See below for details.
<literal>-N</literal>, <literal>-S</literal>, and <literal>-f</literal> <literal>-N</literal>, <literal>-S</literal>, and <literal>-f</literal>
are mutually exclusive. are mutually exclusive.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-n</literal></entry> <entry><literal>-n</literal></entry>
<entry> <entry>
Perform no vacuuming before running the test. Perform no vacuuming before running the test.
This option is <emphasis>necessary</> This option is <emphasis>necessary</>
if you are running a custom test scenario that does not include if you are running a custom test scenario that does not include
the standard tables <structname>pgbench_accounts</>, the standard tables <structname>pgbench_accounts</>,
<structname>pgbench_branches</>, <structname>pgbench_history</>, and <structname>pgbench_branches</>, <structname>pgbench_history</>, and
<structname>pgbench_tellers</>. <structname>pgbench_tellers</>.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-v</literal></entry> <entry><literal>-v</literal></entry>
<entry> <entry>
Vacuum all four standard tables before running the test. Vacuum all four standard tables before running the test.
With neither <literal>-n</> nor <literal>-v</>, pgbench will vacuum the With neither <literal>-n</> nor <literal>-v</>, pgbench will vacuum the
<structname>pgbench_tellers</> and <structname>pgbench_branches</> <structname>pgbench_tellers</> and <structname>pgbench_branches</>
tables, and will truncate <structname>pgbench_history</>. tables, and will truncate <structname>pgbench_history</>.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-D</literal> <replaceable>varname</><literal>=</><replaceable>value</></entry> <entry><literal>-D</literal> <replaceable>varname</><literal>=</><replaceable>value</></entry>
<entry> <entry>
Define a variable for use by a custom script (see below). Define a variable for use by a custom script (see below).
Multiple <literal>-D</> options are allowed. Multiple <literal>-D</> options are allowed.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-C</literal></entry> <entry><literal>-C</literal></entry>
<entry> <entry>
Establish a new connection for each transaction, rather than Establish a new connection for each transaction, rather than
doing it just once per client session. doing it just once per client session.
This is useful to measure the connection overhead. This is useful to measure the connection overhead.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-l</literal></entry> <entry><literal>-l</literal></entry>
<entry> <entry>
Write the time taken by each transaction to a logfile. Write the time taken by each transaction to a logfile.
See below for details. See below for details.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-s</literal> <replaceable>scale_factor</></entry> <entry><literal>-s</literal> <replaceable>scale_factor</></entry>
<entry> <entry>
Report the specified scale factor in <application>pgbench</>'s Report the specified scale factor in <application>pgbench</>'s
output. With the built-in tests, this is not necessary; the output. With the built-in tests, this is not necessary; the
correct scale factor will be detected by counting the number of correct scale factor will be detected by counting the number of
rows in the <structname>pgbench_branches</> table. However, when testing rows in the <structname>pgbench_branches</> table. However, when testing
custom benchmarks (<literal>-f</> option), the scale factor custom benchmarks (<literal>-f</> option), the scale factor
will be reported as 1 unless this option is used. will be reported as 1 unless this option is used.
</entry> </entry>
</row> </row>
<row> <row>
<entry><literal>-d</literal></entry> <entry><literal>-d</literal></entry>
<entry> <entry>
Print debugging output. Print debugging output.
</entry> </entry>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>
<table id="pgbench-common-options"> <table id="pgbench-common-options">
<title><application>pgbench</application> common options</title> <title><application>pgbench</application> common options</title>
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
<entry>Option</entry> <entry>Option</entry>
<entry>Description</entry> <entry>Description</entry>
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row> <row>
<entry><literal>-h</literal> <replaceable>hostname</></entry> <entry><literal>-h</literal> <replaceable>hostname</></entry>
<entry>database server's host</entry> <entry>database server's host</entry>
</row> </row>
<row> <row>
<entry><literal>-p</literal> <replaceable>port</></entry> <entry><literal>-p</literal> <replaceable>port</></entry>
<entry>database server's port</entry> <entry>database server's port</entry>
</row> </row>
<row> <row>
<entry><literal>-U</literal> <replaceable>login</></entry> <entry><literal>-U</literal> <replaceable>login</></entry>
<entry>username to connect as</entry> <entry>username to connect as</entry>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
</table> </table>
</sect2> </sect2>
<sect2> <sect2>
<title>What is the <quote>transaction</> actually performed in pgbench?</title> <title>What is the <quote>transaction</> actually performed in pgbench?</title>
<para> <para>
The default transaction script issues seven commands per transaction: The default transaction script issues seven commands per transaction:
</para> </para>
<orderedlist> <orderedlist>
<listitem><para><literal>BEGIN;</literal></para></listitem> <listitem><para><literal>BEGIN;</literal></para></listitem>
<listitem><para><literal>UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid;</literal></para></listitem> <listitem><para><literal>UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid;</literal></para></listitem>
<listitem><para><literal>SELECT abalance FROM pgbench_accounts WHERE aid = :aid;</literal></para></listitem> <listitem><para><literal>SELECT abalance FROM pgbench_accounts WHERE aid = :aid;</literal></para></listitem>
<listitem><para><literal>UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid;</literal></para></listitem> <listitem><para><literal>UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid;</literal></para></listitem>
<listitem><para><literal>UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;</literal></para></listitem> <listitem><para><literal>UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;</literal></para></listitem>
<listitem><para><literal>INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);</literal></para></listitem> <listitem><para><literal>INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);</literal></para></listitem>
<listitem><para><literal>END;</literal></para></listitem> <listitem><para><literal>END;</literal></para></listitem>
</orderedlist> </orderedlist>
<para> <para>
If you specify <literal>-N</>, steps 4 and 5 aren't included in the If you specify <literal>-N</>, steps 4 and 5 aren't included in the
transaction. If you specify <literal>-S</>, only the <command>SELECT</> is transaction. If you specify <literal>-S</>, only the <command>SELECT</> is
issued. issued.
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Custom Scripts</title> <title>Custom Scripts</title>
<para> <para>
<application>pgbench</application> has support for running custom <application>pgbench</application> has support for running custom
benchmark scenarios by replacing the default transaction script benchmark scenarios by replacing the default transaction script
(described above) with a transaction script read from a file (described above) with a transaction script read from a file
(<literal>-f</literal> option). In this case a <quote>transaction</> (<literal>-f</literal> option). In this case a <quote>transaction</>
counts as one execution of a script file. You can even specify counts as one execution of a script file. You can even specify
multiple scripts (multiple <literal>-f</literal> options), in which multiple scripts (multiple <literal>-f</literal> options), in which
case a random one of the scripts is chosen each time a client session case a random one of the scripts is chosen each time a client session
starts a new transaction. starts a new transaction.
</para> </para>
<para> <para>
The format of a script file is one SQL command per line; multi-line The format of a script file is one SQL command per line; multi-line
SQL commands are not supported. Empty lines and lines beginning with SQL commands are not supported. Empty lines and lines beginning with
<literal>--</> are ignored. Script file lines can also be <literal>--</> are ignored. Script file lines can also be
<quote>meta commands</>, which are interpreted by <application>pgbench</> <quote>meta commands</>, which are interpreted by <application>pgbench</>
itself, as described below. itself, as described below.
</para> </para>
<para> <para>
There is a simple variable-substitution facility for script files. There is a simple variable-substitution facility for script files.
Variables can be set by the command-line <literal>-D</> option, Variables can be set by the command-line <literal>-D</> option,
explained above, or by the meta commands explained below. explained above, or by the meta commands explained below.
In addition to any variables preset by <literal>-D</> command-line options, In addition to any variables preset by <literal>-D</> command-line options,
the variable <literal>scale</> is preset to the current scale factor. the variable <literal>scale</> is preset to the current scale factor.
Once set, a variable's Once set, a variable's
value can be inserted into a SQL command by writing value can be inserted into a SQL command by writing
<literal>:</><replaceable>variablename</>. When running more than <literal>:</><replaceable>variablename</>. When running more than
one client session, each session has its own set of variables. one client session, each session has its own set of variables.
</para> </para>
<para> <para>
Script file meta commands begin with a backslash (<literal>\</>). Script file meta commands begin with a backslash (<literal>\</>).
Arguments to a meta command are separated by white space. Arguments to a meta command are separated by white space.
These meta commands are supported: These meta commands are supported:
</para> </para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term> <term>
<literal>\set <replaceable>varname</> <replaceable>operand1</> [ <replaceable>operator</> <replaceable>operand2</> ]</literal> <literal>\set <replaceable>varname</> <replaceable>operand1</> [ <replaceable>operator</> <replaceable>operand2</> ]</literal>
</term> </term>
<listitem> <listitem>
<para> <para>
Sets variable <replaceable>varname</> to a calculated integer value. Sets variable <replaceable>varname</> to a calculated integer value.
Each <replaceable>operand</> is either an integer constant or a Each <replaceable>operand</> is either an integer constant or a
<literal>:</><replaceable>variablename</> reference to a variable <literal>:</><replaceable>variablename</> reference to a variable
having an integer value. The <replaceable>operator</> can be having an integer value. The <replaceable>operator</> can be
<literal>+</>, <literal>-</>, <literal>*</>, or <literal>/</>. <literal>+</>, <literal>-</>, <literal>*</>, or <literal>/</>.
</para> </para>
<para> <para>
Example: Example:
<programlisting> <programlisting>
\set ntellers 10 * :scale \set ntellers 10 * :scale
</programlisting> </programlisting>
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
<literal>\setrandom <replaceable>varname</> <replaceable>min</> <replaceable>max</></literal> <literal>\setrandom <replaceable>varname</> <replaceable>min</> <replaceable>max</></literal>
</term> </term>
<listitem> <listitem>
<para> <para>
Sets variable <replaceable>varname</> to a random integer value Sets variable <replaceable>varname</> to a random integer value
between the limits <replaceable>min</> and <replaceable>max</> inclusive. between the limits <replaceable>min</> and <replaceable>max</> inclusive.
Each limit can be either an integer constant or a Each limit can be either an integer constant or a
<literal>:</><replaceable>variablename</> reference to a variable <literal>:</><replaceable>variablename</> reference to a variable
having an integer value. having an integer value.
</para> </para>
<para> <para>
Example: Example:
<programlisting> <programlisting>
\setrandom aid 1 :naccounts \setrandom aid 1 :naccounts
</programlisting> </programlisting>
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
<literal>\sleep <replaceable>number</> [ us | ms | s ]</literal> <literal>\sleep <replaceable>number</> [ us | ms | s ]</literal>
</term> </term>
<listitem> <listitem>
<para> <para>
Causes script execution to sleep for the specified duration in Causes script execution to sleep for the specified duration in
microseconds (<literal>us</>), milliseconds (<literal>ms</>) or seconds microseconds (<literal>us</>), milliseconds (<literal>ms</>) or seconds
(<literal>s</>). If the unit is omitted then seconds are the default. (<literal>s</>). If the unit is omitted then seconds are the default.
<replaceable>number</> can be either an integer constant or a <replaceable>number</> can be either an integer constant or a
<literal>:</><replaceable>variablename</> reference to a variable <literal>:</><replaceable>variablename</> reference to a variable
having an integer value. having an integer value.
</para> </para>
<para> <para>
Example: Example:
<programlisting> <programlisting>
\sleep 10 ms \sleep 10 ms
</programlisting> </programlisting>
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
<literal>\setshell <replaceable>varname</> <replaceable>command</> [ <replaceable>argument</> ... ]</literal> <literal>\setshell <replaceable>varname</> <replaceable>command</> [ <replaceable>argument</> ... ]</literal>
</term> </term>
<listitem> <listitem>
<para> <para>
Sets variable <replaceable>varname</> to the result of the shell command Sets variable <replaceable>varname</> to the result of the shell command
<replaceable>command</>. The command must return an integer value <replaceable>command</>. The command must return an integer value
through its standard output. through its standard output.
</para> </para>
<para> <para>
<replaceable>argument</> can be either a text constant or a <replaceable>argument</> can be either a text constant or a
<literal>:</><replaceable>variablename</> reference to a variable of <literal>:</><replaceable>variablename</> reference to a variable of
any types. If you want to use <replaceable>argument</> starting with any types. If you want to use <replaceable>argument</> starting with
colons, you need to add an additional colon at the beginning of colons, you need to add an additional colon at the beginning of
<replaceable>argument</>. <replaceable>argument</>.
</para> </para>
<para> <para>
Example: Example:
<programlisting> <programlisting>
\setshell variable_to_be_assigned command literal_argument :variable ::literal_starting_with_colon \setshell variable_to_be_assigned command literal_argument :variable ::literal_starting_with_colon
</programlisting> </programlisting>
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
<literal>\shell <replaceable>command</> [ <replaceable>argument</> ... ]</literal> <literal>\shell <replaceable>command</> [ <replaceable>argument</> ... ]</literal>
</term> </term>
<listitem> <listitem>
<para> <para>
Same as <literal>\setshell</literal>, but the result is ignored. Same as <literal>\setshell</literal>, but the result is ignored.
</para> </para>
<para> <para>
Example: Example:
<programlisting> <programlisting>
\shell command literal_argument :variable ::literal_starting_with_colon \shell command literal_argument :variable ::literal_starting_with_colon
</programlisting> </programlisting>
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
<para> <para>
As an example, the full definition of the built-in TPC-B-like As an example, the full definition of the built-in TPC-B-like
transaction is: transaction is:
<programlisting> <programlisting>
\set nbranches :scale \set nbranches :scale
\set ntellers 10 * :scale \set ntellers 10 * :scale
\set naccounts 100000 * :scale \set naccounts 100000 * :scale
\setrandom aid 1 :naccounts \setrandom aid 1 :naccounts
\setrandom bid 1 :nbranches \setrandom bid 1 :nbranches
\setrandom tid 1 :ntellers \setrandom tid 1 :ntellers
\setrandom delta -5000 5000 \setrandom delta -5000 5000
BEGIN; BEGIN;
UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid; UPDATE pgbench_accounts SET abalance = abalance + :delta WHERE aid = :aid;
SELECT abalance FROM pgbench_accounts WHERE aid = :aid; SELECT abalance FROM pgbench_accounts WHERE aid = :aid;
UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid; UPDATE pgbench_tellers SET tbalance = tbalance + :delta WHERE tid = :tid;
UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid; UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;
INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP); INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);
END; END;
</programlisting> </programlisting>
This script allows each iteration of the transaction to reference This script allows each iteration of the transaction to reference
different, randomly-chosen rows. (This example also shows why it's different, randomly-chosen rows. (This example also shows why it's
important for each client session to have its own variables &mdash; important for each client session to have its own variables &mdash;
otherwise they'd not be independently touching different rows.) otherwise they'd not be independently touching different rows.)
</para> </para>
</sect2> </sect2>
<sect2> <sect2>
<title>Per-transaction logging</title> <title>Per-transaction logging</title>
<para> <para>
With the <literal>-l</> option, <application>pgbench</> writes the time With the <literal>-l</> option, <application>pgbench</> writes the time
taken by each transaction to a logfile. The logfile will be named taken by each transaction to a logfile. The logfile will be named
<filename>pgbench_log.<replaceable>nnn</></filename>, where <filename>pgbench_log.<replaceable>nnn</></filename>, where
<replaceable>nnn</> is the PID of the pgbench process. <replaceable>nnn</> is the PID of the pgbench process.
The format of the log is: If the <literal>-j</> option is 2 or higher, creating multiple worker
threads, each will have its own log file. The first worker will use the
<programlisting> the same name for its log file as in the standard single worker case.
<replaceable>client_id</> <replaceable>transaction_no</> <replaceable>time</> <replaceable>file_no</> <replaceable>time_epoch</> <replaceable>time_us</> The additional log files for the other workers will be named
</programlisting> <filename>pgbench_log.<replaceable>nnn</>.<replaceable>mmm</></filename>,
where <replaceable>mmm</> is a sequential number for each worker starting
where <replaceable>time</> is the elapsed transaction time in microseconds, with 1.
<replaceable>file_no</> identifies which script file was used </para>
(useful when multiple scripts were specified with <literal>-f</>),
and <replaceable>time_epoch</>/<replaceable>time_us</> are a <para>
UNIX epoch format timestamp and an offset The format of the log is:
in microseconds (suitable for creating a ISO 8601
timestamp with fractional seconds) showing when <programlisting>
the transaction completed. <replaceable>client_id</> <replaceable>transaction_no</> <replaceable>time</> <replaceable>file_no</> <replaceable>time_epoch</> <replaceable>time_us</>
</para> </programlisting>
<para> where <replaceable>time</> is the elapsed transaction time in microseconds,
Here are example outputs: <replaceable>file_no</> identifies which script file was used
<programlisting> (useful when multiple scripts were specified with <literal>-f</>),
0 199 2241 0 1175850568 995598 and <replaceable>time_epoch</>/<replaceable>time_us</> are a
0 200 2465 0 1175850568 998079 UNIX epoch format timestamp and an offset
0 201 2513 0 1175850569 608 in microseconds (suitable for creating a ISO 8601
0 202 2038 0 1175850569 2663 timestamp with fractional seconds) showing when
</programlisting> the transaction completed.
</para> </para>
</sect2>
<para>
<sect2> Here are example outputs:
<title>Good Practices</title> <programlisting>
0 199 2241 0 1175850568 995598
<para> 0 200 2465 0 1175850568 998079
It is very easy to use <application>pgbench</> to produce completely 0 201 2513 0 1175850569 608
meaningless numbers. Here are some guidelines to help you get useful 0 202 2038 0 1175850569 2663
results. </programlisting>
</para> </para>
</sect2>
<para>
In the first place, <emphasis>never</> believe any test that runs <sect2>
for only a few seconds. Use the <literal>-t</> or <literal>-T</> option <title>Good Practices</title>
to make the run last at least a few minutes, so as to average out noise.
In some cases you could need hours to get numbers that are reproducible. <para>
It's a good idea to try the test run a few times, to find out if your It is very easy to use <application>pgbench</> to produce completely
numbers are reproducible or not. meaningless numbers. Here are some guidelines to help you get useful
</para> results.
</para>
<para>
For the default TPC-B-like test scenario, the initialization scale factor <para>
(<literal>-s</>) should be at least as large as the largest number of In the first place, <emphasis>never</> believe any test that runs
clients you intend to test (<literal>-c</>); else you'll mostly be for only a few seconds. Use the <literal>-t</> or <literal>-T</> option
measuring update contention. There are only <literal>-s</> rows in to make the run last at least a few minutes, so as to average out noise.
the <structname>pgbench_branches</> table, and every transaction wants to In some cases you could need hours to get numbers that are reproducible.
update one of them, so <literal>-c</> values in excess of <literal>-s</> It's a good idea to try the test run a few times, to find out if your
will undoubtedly result in lots of transactions blocked waiting for numbers are reproducible or not.
other transactions. </para>
</para>
<para>
<para> For the default TPC-B-like test scenario, the initialization scale factor
The default test scenario is also quite sensitive to how long it's been (<literal>-s</>) should be at least as large as the largest number of
since the tables were initialized: accumulation of dead rows and dead space clients you intend to test (<literal>-c</>); else you'll mostly be
in the tables changes the results. To understand the results you must keep measuring update contention. There are only <literal>-s</> rows in
track of the total number of updates and when vacuuming happens. If the <structname>pgbench_branches</> table, and every transaction wants to
autovacuum is enabled it can result in unpredictable changes in measured update one of them, so <literal>-c</> values in excess of <literal>-s</>
performance. will undoubtedly result in lots of transactions blocked waiting for
</para> other transactions.
</para>
<para>
A limitation of <application>pgbench</> is that it can itself become <para>
the bottleneck when trying to test a large number of client sessions. The default test scenario is also quite sensitive to how long it's been
This can be alleviated by running <application>pgbench</> on a different since the tables were initialized: accumulation of dead rows and dead space
machine from the database server, although low network latency will be in the tables changes the results. To understand the results you must keep
essential. It might even be useful to run several <application>pgbench</> track of the total number of updates and when vacuuming happens. If
instances concurrently, on several client machines, against the same autovacuum is enabled it can result in unpredictable changes in measured
database server. performance.
</para> </para>
</sect2>
<para>
</sect1> A limitation of <application>pgbench</> is that it can itself become
the bottleneck when trying to test a large number of client sessions.
This can be alleviated by running <application>pgbench</> on a different
machine from the database server, although low network latency will be
essential. It might even be useful to run several <application>pgbench</>
instances concurrently, on several client machines, against the same
database server.
</para>
</sect2>
</sect1>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment