Update the speed comparison documentation to show the improved performance

of PostgreSQL after performance tuning. (CVS 869)

FossilOrigin-Name: 73c904e57a158820705daf5737e0fc825cfe1aea
This commit is contained in:
drh 2003-02-16 22:36:03 +00:00
parent 94e9203247
commit ad636221bb
3 changed files with 26 additions and 14 deletions

View File

@ -1,5 +1,5 @@
C Added\stest\scode\sto\scheck\sfor\sfile\sdescriptor\sleaks.\s\sAll\sregression\stests\spass\nnow\son\sboth\swin2k\sand\slinux.\s(CVS\s868)
D 2003-02-16T22:21:32
C Update\sthe\sspeed\scomparison\sdocumentation\sto\sshow\sthe\simproved\sperformance\nof\sPostgreSQL\safter\sperformance\stuning.\s(CVS\s869)
D 2003-02-16T22:36:03
F Makefile.in 6606854b1512f185b8e8c779b8d7fc2750463d64
F Makefile.linux-gcc b86a99c493a5bfb402d1d9178dcdc4bd4b32f906
F README f1de682fbbd94899d50aca13d387d1b3fd3be2dd
@ -151,11 +151,11 @@ F www/nulls.tcl 29497dac2bc5b437aa7e2e94577dad4d8933ed26
F www/omitted.tcl 118062f40a203fcb88b8d68ef1d7c0073ac191ec
F www/opcode.tcl 33c5f2061a05c5d227c72b84c080b3bf74c74f8b
F www/quickstart.tcl 4e97bef825e6a4153c43afb9f97235fc4da278ab
F www/speed.tcl 4d463e2aea41f688ed320a937f93ff885be918c3
F www/speed.tcl cb4c10a722614aea76d2c51f32ee43400d5951be
F www/sqlite.tcl ae3dcfb077e53833b59d4fcc94d8a12c50a44098
F www/tclsqlite.tcl 1db15abeb446aad0caf0b95b8b9579720e4ea331
F www/vdbe.tcl 2013852c27a02a091d39a766bc87cff329f21218
P d10adc1c5727d76320d5919be55e86d030e9c8bc
R 64431a6b1a331d6ad8bd869629c988f8
P 75ba78280f7ab6b6acce5878859312f3223ee898
R 24a2ec5fee02b8a78fc04a7b84369346
U drh
Z 0930ffd5b3a1b2b8d49d4e03a67a30f6
Z 2e49fb8d065665f41dfa451c67c5a8d9

View File

@ -1 +1 @@
75ba78280f7ab6b6acce5878859312f3223ee898
73c904e57a158820705daf5737e0fc825cfe1aea

View File

@ -1,7 +1,7 @@
#
# Run this Tcl script to generate the speed.html file.
#
set rcsid {$Id: speed.tcl,v 1.10 2003/01/25 14:25:42 drh Exp $ }
set rcsid {$Id: speed.tcl,v 1.11 2003/02/16 22:36:03 drh Exp $ }
puts {<html>
<head>
@ -27,8 +27,8 @@ conclusions drawn from these experiments:
<ul>
<li><p>
SQLite 2.7.6 is significantly faster (sometimes as much as 10 or
20 times faster) than PostgreSQL 7.1.3
for most common operations.
20 times faster) than the default PostgreSQL 7.1.3 installation
on RedHat 7.3 for most common operations.
</p></li>
<li><p>
SQLite 2.7.6 is often faster (sometimes
@ -76,14 +76,26 @@ No effort was made to tune these engines. Note in particular
the the default MySQL configuration on RedHat 7.2 does not support
transactions. Not having to support transactions gives MySQL a
big speed advantage, but SQLite is still able to hold its own on most
tests. On the other hand, I am told that the default PostgreSQL
configuration is unnecessarily conservative (it is designed to
tests.
</p>
<p>
I am told that the default PostgreSQL configuration in RedHat 7.3
is unnecessarily conservative (it is designed to
work on a machine with 8MB of RAM) and that PostgreSQL could
be made to run a lot faster with some knowledgable configuration
tuning. I have not, however, been able to personally confirm
these reports.
tuning.
Matt Sergeant reports that he has tuned his PostgreSQL installation
and rerun the tests shown below. His results show that
PostgreSQL and MySQL run at about the same speed. For Matt's
results, visit
</p>
<blockquote>
<a href="http://www.sergeant.org/sqlite_vs_pgsync.html">
http://www.sergeant.org/sqlite_vs_pgsync.html</a>
</blockquote>
<p>
SQLite was tested in the same configuration that it appears
on the website. It was compiled with -O6 optimization and with