INN and db 4,6

[Russ Allbery]

Marc Stürmer <mail at marc-stuermer.de> writes:

> Since all of the requests to an external DB need to run first through
> the OS and then through the engine and back it's of course faster to
> just skip all of this overhead and embed an engine instead. An external
> DB would also need added maintenance sometimes and when it hangs,
> well... ok, BDB is also externally implemented, but is still a more
> lightweight solution than MySQL/Postgres.

Yeah, and there's a long history of people not believing this and arguing
with people on the OpenLDAP list about it, but when you do actual
benchmarks, a properly tuned BerkeleyDB database just destroys a properly
tuned MySQL database, no matter what engine you use, for speed.  It's not
just a little bit faster.  It's integer factors faster.

> So the best bet if possible and wanted would be to use an embeddable SQL
> engine like SQLite.

Which would be even slower.

You can do anything you want with a small server; any of those options
would be fine.  But for a small server, why not just use tradindexed and
get much better recovery properties?

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.