Announcement: pgbench-1.1 released

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: hackers(at)postgreSQL(dot)org
Subject: Announcement: pgbench-1.1 released
Date: 1999-09-30 01:15:59
Message-ID: 199909300115.KAA01268@ext16.sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Hi,

I have made a small tool called "pgbench," that may be useful for
some stress testings and performance measurements for PostgreSQL.
pgbench can be obtained from:

ftp://ftp.sra.co.jp/pub/cmd/postgres/pgbench/

Pgbench runs small transactions similar to TPC-B concurrently and
reports the number of transactions actually done per second (tps).
Pgbench uses the asynchronous functions of libpq to simulate
concurrent clients. Example outputs from pgbench are shown below:

number of clients: 4
number of transactions per client: 100
number of processed transactions: 400/400
tps = 19.875015(including connections establishing)
tps = 20.098827(excluding connections establishing)

(above result was reported on my PowerBook with 603e CPU(180MHz), 80MB
mem running PostgreSQL 6.5.2 with -F option, and Linux 2.2.1 kernel)

Pgbench does not require any special libraries other than libpq. It
comes with a configure script and should be very easy to build.

*CAUTION*
pgbench will blow away tables named accounts, branches, history and
tellers. It is best to create a new database for pgbench before
running it.

BTW, the greatest tps I have ever seen was around 260 on a Linux box
running RedHat 6.0, having 2 Pentiumn III 600MHz CPUs and 512MB mem.

Enjoy,
---
Tatsuo Ishii

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-09-30 01:16:22 Re: [HACKERS] shared memory 651, freebsd 2.2.7
Previous Message Bruce Momjian 1999-09-30 01:15:46 Re: [HACKERS] Re: New notices?

Browse pgsql-interfaces by date

  From Date Subject
Next Message ALPESH KOTHARI 1999-09-30 01:28:47 JDBC problem with string
Previous Message Spirou 1999-09-29 22:24:34 Re: [INTERFACES] psql trerminal behaviour