postgres.benchmark 3.42 KB
Newer Older
1
# This file describes how to run MySQL benchmark suite with PostgreSQL
2 3 4 5 6 7
#
# WARNING:
#
# Don't run the --fast test on a PostgreSQL 7.1.1 database on
# which you have any critical data; During one of our test runs
# PostgreSQL got a corrupted database and all data was destroyed!
8
# When we tried to restart postmaster, It died with a
9 10
# 'no such file or directory' error and never recovered from that!
#
11 12 13
# Another time vacuum() filled our system disk with had 6G free
# while vaccuming a table of 60 M.
#
14
# WARNING
15 16

# The test was run on a Intel Xeon 2x 550 Mzh machine with 1G memory,
17
# 9G hard disk.  The OS is Suse 7.1, with Linux 2.4.2 compiled with SMP
18 19 20 21
# support
# Both the perl client and the database server is run
# on the same machine. No other cpu intensive process was used during
# the benchmark.
22 23 24 25 26 27
#
# During the test we run PostgreSQL with -o -F, not async mode (not ACID safe)
# because when we started postmaster without -o -F, PostgreSQL log files
# filled up a 9G disk until postmaster crashed.
# We did however notice that with -o -F, PostgreSQL was a magnitude slower
# than when not using -o -F.
28

29 30
#
# First, install postgresql-7.1.2.tar.gz
31

32
# Adding the following lines to your ~/.bash_profile or
33 34
# corresponding file. If you are using csh, use ´setenv´.

35 36
export POSTGRES_INCLUDE=/usr/local/pg/include
export POSTGRES_LIB=/usr/local/pg/lib
37

38 39
PATH=$PATH:/usr/local/pg/bin
MANPATH=$MANPATH:/usr/local/pg/man
40 41 42 43 44

#
# Add the following line to /etc/ld.so.conf:
#

45
/usr/local/pg/lib
46 47 48 49

# and run:

ldconfig
50

51 52
# untar the postgres source distribution,  cd to postgresql-*
# and run the following commands:
53

54
CFLAGS=-O3 ./configure
55 56 57
gmake
gmake install

58 59
mkdir /usr/local/pg/data
chown postgres /usr/local/pg/data
60
su - postgres
61 62 63 64
/usr/local/pg/bin/initdb -D /usr/local/pg/data
/usr/local/pg/bin/postmaster -o -F -D /usr/local/pg/data &
/usr/local/pg/bin/createdb test
exit
65 66

#
67
# Second, install packages DBD-Pg-1.00.tar.gz and DBI-1.18.tar.gz,
68
# available from http://www.perl.com/CPAN/
69 70 71 72 73 74

export POSTGRES_LIB=/usr/local/pg/lib/
export POSTGRES_INCLUDE=/usr/local/pg/include/postgresql
perl Makefile.PL
make
make install
75 76 77 78 79 80 81 82

#
# Now we run the test that can be found in the sql-bench directory in the
# MySQL 3.23 source distribution.
#
# We did run two tests:
# The standard test

83
run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512M, pg started with -o -F" --user=postgres --server=pg --cmp=mysql
84

85 86
# When running with --fast we run the following vacuum commands on
# the database between each major update of the tables:
87
# vacuum anlyze table
88 89
# vacuum table
# or
90
# vacuum analyze
91 92 93 94
# vacuum

# The time for vacuum() is accounted for in the book-keeping() column, not
# in the test that updates the database.
95

96
run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512M, pg started with -o -F" --user=postgres --server=pg --cmp=mysql --fast
97 98 99 100 101

# If you want to store the results in a output/RUN-xxx file, you should
# repeate the benchmark with the extra option --log --use-old-result
# This will create a the RUN file based of the previous results

102 103
run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512M, pg started with -o -F" --user=postgres --server=pg --cmp=mysql --log --use-old-result
run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512MG, pg started with -o -F" --user=postgres --server=pg --cmp=mysql --fast --log --use-old-result
104 105 106 107

# Between running the different tests we dropped and recreated the PostgreSQL
# database to ensure that PostgreSQL should get a clean start,
# independent of the previous runs.