diff options
Diffstat (limited to 'sql-bench/Comments/postgres.benchmark')
| -rw-r--r-- | sql-bench/Comments/postgres.benchmark | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/sql-bench/Comments/postgres.benchmark b/sql-bench/Comments/postgres.benchmark index b25a9931f9e..c52a53699e0 100644 --- a/sql-bench/Comments/postgres.benchmark +++ b/sql-bench/Comments/postgres.benchmark @@ -11,24 +11,26 @@ # Another time vacuum() filled our system disk with had 6G free # while vaccuming a table of 60 M. # -# We have sent a mail about this to the PostgreSQL mailing list, so -# the PostgreSQL developers should be aware of these problems and should -# hopefully fix this soon. -# # WARNING # The test was run on a Intel Xeon 2x 550 Mzh machine with 1G memory, -# 9G hard disk. The OS is Suse 7.1, with Linux 2.4.0 compiled with SMP +# 9G hard disk. The OS is Suse 7.1, with Linux 2.4.2 compiled with SMP # 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. +# +# 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. -# First, install postgresql-7.1.1.tar.gz +# +# First, install postgresql-7.1.2.tar.gz # Adding the following lines to your ~/.bash_profile or # corresponding file. If you are using csh, use īsetenvī. -# export POSTGRES_INCLUDE=/usr/local/pg/include export POSTGRES_LIB=/usr/local/pg/lib @@ -62,7 +64,7 @@ su - postgres exit # -# Second, install packages DBD-Pg-1.00.tar.gz and DBI-1.14.tar.gz, +# Second, install packages DBD-Pg-1.00.tar.gz and DBI-1.18.tar.gz, # available from http://www.perl.com/CPAN/ export POSTGRES_LIB=/usr/local/pg/lib/ @@ -82,6 +84,7 @@ run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512M, pg started with -o -F" --u # When running with --fast we run the following vacuum commands on # the database between each major update of the tables: +# vacuum anlyze table # vacuum table # or # vacuum analyze |