* Michael Watkins wrote on [2007-08-24 02:44:24 -0700]:
> I've done a little (very little) performance testing mostly to prove
> out some ideas and I must say I'm very impressed with the Sqlite
> behaviour - in limited testing its not much slower overall than
> native FileStorage2 or ShelfStorage but has the great advantage of
> almost instant start up time.

Further on this, some examples:

Writes -- Create a new storage (new database/file), initialize root,
create a NewsDatabase, add N NewsItem objects (all N NewsItem
objects are within one Durus (and sql) commit).

(all times in seconds)
N                   5,000   50,000
ShelfStorage         5.26    52.45
FileStorage2         5.03    58.88
SqliteStorage        5.72    56.65
PostgresqlStorage   12.46   138.90


Reads               Time to   Retrieve  Random
50,000 recs         Root      1 record  10      100     1000
ShelfStorage          2.23      0.005   0.077   0.214   0.882
FileStorage2          1.35      0.005   0.075   0.213   0.862
SqliteStorage         0.039     0.007   0.099   0.299   1.173
PostgresqlStorage     0.019     0.011   0.087   0.320   1.448

I've not had a chance to look at a ClientStorage accessing a Durus
server backended by one of these SQL based storages.

Your mileage may varying'ly yours,
mw