Skip to content

Commit 4c4bf7a

Browse files
author
Andrey Lebedev
committed
benchmarks says something completely different...
1 parent 0dc5494 commit 4c4bf7a

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

doc/installation.txt

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Installing Roundup
33
==================
44

5-
:Version: $Revision: 1.47 $
5+
:Version: $Revision: 1.48 $
66

77
.. contents::
88

@@ -240,12 +240,10 @@ There's several to choose from, each with benefits and limitations:
240240
There are no limitations, and it's much faster and more scaleable than the
241241
dbm backends.
242242
**mysql**
243-
Backend for popular RDBMS MySQL. This backend uses MySQL's Berkeley DB
244-
(transaction safe) table format, so with small amount of data it may be a
245-
bit slower than \*dbm backends (due to mysql layer's overhead). However with
246-
lots of data mysql may perform better (due to query optimisation). No actual
247-
serious benchmarks were made though. For more info on installation of this
248-
backend see doc/mysql.txt.
243+
Backend for popular RDBMS MySQL. According to benchmarks, this backend works
244+
much faster than any of *dbm ones, but slightly slower than metakit and
245+
sqlite. A good scalability is not a property of this backend for now,
246+
though. For more info on backend installation see doc/mysql.txt.
249247
**metakit**
250248
This backend is implemented over the metakit_ storage system, using Mk4Py as
251249
the interface. It scales much better than the dbm backends.

0 commit comments

Comments
 (0)