changeset 1595:1ae674595c04

benchmarks says something completely different...
author Andrey Lebedev <kedder@users.sourceforge.net>
date Sat, 19 Apr 2003 09:57:27 +0000
parents eee8b5eecb33
children 33a0d94c7658
files doc/installation.txt
diffstat 1 files changed, 5 insertions(+), 7 deletions(-) [+]
line wrap: on
line diff
--- a/doc/installation.txt	Sat Apr 19 05:03:54 2003 +0000
+++ b/doc/installation.txt	Sat Apr 19 09:57:27 2003 +0000
@@ -2,7 +2,7 @@
 Installing Roundup
 ==================
 
-:Version: $Revision: 1.47 $
+:Version: $Revision: 1.48 $
 
 .. contents::
 
@@ -240,12 +240,10 @@
   There are no limitations, and it's much faster and more scaleable than the
   dbm backends.
 **mysql**
-  Backend for popular RDBMS MySQL. This backend uses MySQL's Berkeley DB
-  (transaction safe) table format, so with small amount of data it may be a
-  bit slower than \*dbm backends (due to mysql layer's overhead). However with
-  lots of data mysql may perform better (due to query optimisation). No actual
-  serious benchmarks were made though. For more info on installation of this
-  backend see doc/mysql.txt. 
+  Backend for popular RDBMS MySQL. According to benchmarks, this backend works
+  much faster than any of *dbm ones, but slightly slower than metakit and
+  sqlite. A good scalability is not a property of this backend for now,
+  though. For more info on backend installation see doc/mysql.txt. 
 **metakit**
   This backend is implemented over the metakit_ storage system, using Mk4Py as
   the interface. It scales much better than the dbm backends.

Roundup Issue Tracker: http://roundup-tracker.org/