Mercurial > p > roundup > code
comparison doc/installation.txt @ 2179:5aa74f9879ac
rework the backend selection bit
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Mon, 05 Apr 2004 00:51:00 +0000 |
| parents | 98656054ccfa |
| children | 3f89c8ffe4f1 |
comparison
equal
deleted
inserted
replaced
| 2178:e1a481838a32 | 2179:5aa74f9879ac |
|---|---|
| 1 ================== | 1 ================== |
| 2 Installing Roundup | 2 Installing Roundup |
| 3 ================== | 3 ================== |
| 4 | 4 |
| 5 :Version: $Revision: 1.70 $ | 5 :Version: $Revision: 1.71 $ |
| 6 | 6 |
| 7 .. contents:: | 7 .. contents:: |
| 8 | 8 |
| 9 | 9 |
| 10 Overview | 10 Overview |
| 257 --------------------- | 257 --------------------- |
| 258 | 258 |
| 259 The actual storage of Roundup tracker information is handled by backends. | 259 The actual storage of Roundup tracker information is handled by backends. |
| 260 There's several to choose from, each with benefits and limitations: | 260 There's several to choose from, each with benefits and limitations: |
| 261 | 261 |
| 262 **anydbm** | 262 ========== =========== ===== ============================== |
| 263 This backend is guaranteed to work on any system that Python runs on. It | 263 Name Speed Users Support |
| 264 will generally choose the best dbm backend that is available on your system | 264 ========== =========== ===== ============================== |
| 265 (from the list dbhash, gdbm, dbm, dumbdbm). It is the least scaleable of all | 265 anydbm Slowest Few Always available |
| 266 backends, but performs well enough for a smallish tracker (a couple of | 266 bsddb Slow Few Usually available |
| 267 thousand issues, under fifty users, ...). | 267 sqlite Fastest(*) Few Needs install (SQLite_) |
| 268 **bsddb** | 268 metakit Fastest(*) Few Needs install (metakit_) |
| 269 This effectively the same as anydbm, but uses the bsddb backend. This allows | 269 postgresql Fast Many Needs install/admin (psycopg_) |
| 270 it to gain some performance and scaling benefits. | 270 mysql Fast Many Needs install/admin (MySQLdb_) |
| 271 **bsddb3** | 271 ========== =========== ===== ============================== |
| 272 Again, this effectively the same as anydbm, but uses the bsddb3 backend. | 272 |
| 273 This allows it to gain some performance and scaling benefits. | 273 **sqlite** and **metakit** |
| 274 **sqlite** | 274 These use the embedded database engines SQLite_ and metakit_ to provide |
| 275 This uses the SQLite_ embedded RDBMS to provide a fast, scaleable backend. | 275 very fast backends. They are not suitable for trackers which will have |
| 276 There are no limitations, and it's much faster and more scaleable than the | 276 many simultaneous users. |
| 277 dbm backends. | 277 **postgresql** |
| 278 Backend for popular RDBMS PostgreSQL. You must read doc/postgresql.txt for | |
| 279 additional installation steps and requirements. | |
| 278 **mysql** | 280 **mysql** |
| 279 Backend for popular RDBMS MySQL. According to benchmarks, this backend works | 281 Backend for popular RDBMS MySQL. You must read doc/mysql.txt for additional |
| 280 much faster than any of \*dbm ones, but slightly slower than metakit and | 282 installation steps and requirements. |
| 281 sqlite. You must read doc/mysql.txt for additional installation steps and | 283 |
| 282 requirements. | 284 You may defer your decision by setting your tracker up with the anydbm |
| 283 **postgresql** | 285 backend (which is guaranteed to be available) and switching to one of the |
| 284 Backend for popular RDBMS PostgreSQL. According to benchmarks, this | 286 other backends at any time using the instructions in the `administration |
| 285 backend works much faster than any of \*dbm ones and mysql, but slightly | 287 guide`_. |
| 286 slower than metakit and sqlite. You must read doc/postgresql.txt for | |
| 287 additional installation steps and requirements. | |
| 288 **metakit** | |
| 289 This backend is implemented over the metakit_ storage system, using Mk4Py as | |
| 290 the interface. It scales much better than the dbm backends. | |
| 291 | |
| 292 You should be wary of using all but the mysql backend with high-volume trackers | |
| 293 (requests every second or two) as database locking is done on the whole | |
| 294 database. | |
| 295 | |
| 296 You may set your tracker up with the anydbm backend (which is guaranteed to be | |
| 297 available) and switch to one of the other backends at any time using the | |
| 298 instructions in the `administration guide`_. | |
| 299 | 288 |
| 300 | 289 |
| 301 Configure a Web Interface | 290 Configure a Web Interface |
| 302 ------------------------- | 291 ------------------------- |
| 303 | 292 |
| 620 .. _`customising roundup`: customizing.html | 609 .. _`customising roundup`: customizing.html |
| 621 .. _`upgrading document`: upgrading.html | 610 .. _`upgrading document`: upgrading.html |
| 622 .. _`administration guide`: admin_guide.html | 611 .. _`administration guide`: admin_guide.html |
| 623 .. _sqlite: http://www.hwaci.com/sw/sqlite/ | 612 .. _sqlite: http://www.hwaci.com/sw/sqlite/ |
| 624 .. _metakit: http://www.equi4.com/metakit/ | 613 .. _metakit: http://www.equi4.com/metakit/ |
| 625 | 614 .. _Psycopg: http://initd.org/software/initd/psycopg |
| 615 .. _MySQLdb: http://sourceforge.net/projects/mysql-python | |
| 616 |