diff options
| author | unknown <monty@hundin.mysql.fi> | 2001-06-05 04:05:33 +0300 |
|---|---|---|
| committer | unknown <monty@hundin.mysql.fi> | 2001-06-05 04:05:33 +0300 |
| commit | b1e00c96809479e5de09aa97509883ea96274b57 (patch) | |
| tree | b952b185420f1578799b95526a1c2eeb16a583b9 /sql-bench/Comments | |
| parent | 9d77fddc79b6d1d19ea81aa15f4214dc46d72374 (diff) | |
| download | mariadb-git-b1e00c96809479e5de09aa97509883ea96274b57.tar.gz | |
Updated benchmarks and crash-me for postgreSQL 7.1.1
Fixed option for symlinks
Docs/manual.texi:
Updated symlink handling.
sql-bench/Comments/postgres.benchmark:
Updated benchmark text
sql-bench/Makefile.am:
Added graph-compare-results
sql-bench/compare-results.sh:
Don't reset the cmp option.
sql-bench/crash-me.sh:
Updated transaction testing.
sql-bench/limits/mysql-3.23.cfg:
Updated benchmark run
sql-bench/limits/mysql.cfg:
Updated benchmark run
sql-bench/limits/pg.cfg:
Updated benchmark run
sql-bench/server-cfg.sh:
Don't do vacuum too often.
sql-bench/test-insert.sh:
Don't do vacuum too often.
sql/mysqld.cc:
Changed skip-symlinks to skip-symlink
Diffstat (limited to 'sql-bench/Comments')
| -rw-r--r-- | sql-bench/Comments/postgres.benchmark | 19 |
1 files changed, 16 insertions, 3 deletions
diff --git a/sql-bench/Comments/postgres.benchmark b/sql-bench/Comments/postgres.benchmark index cce9a8f05fe..4b417b8f97e 100644 --- a/sql-bench/Comments/postgres.benchmark +++ b/sql-bench/Comments/postgres.benchmark @@ -5,9 +5,16 @@ # 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! -# (When we tried to restart postmaster, It died with a +# When we tried to restart postmaster, It died with a # 'no such file or directory' error and never recovered from that! # +# 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, @@ -73,8 +80,14 @@ make install run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512M, pg started with -o -F" --user=postgres --server=pg --cmp=mysql -# and a test where we do a vacuum() after each update. -# (The time for vacuum() is counted in the book-keeping() column) +# When running with --fast we run the following vacuum commands on +# the database between each major update of the tables: +# vacuum table +# or +# vacuum + +# The time for vacuum() is accounted for in the book-keeping() column, not +# in the test that updates the database. run-all-tests --comment="Intel Xeon, 2x550 Mhz, 512M, pg started with -o -F" --user=postgres --server=pg --cmp=mysql --fast |