Michael Ludwig wrote:

> A common way for a DBMS to increase transaction throughput is to
> maintain a sequential log of transactions that records all changes and
> allows the engine to defer writing of the data to the actual storage
> location to a future, calm moment. The point here is that appending data
> to the end of the log is faster than doing random disk seeks. Searching
> for "sequential transaction log" will bring up some information.
>
> This does not seem to be the way Firebird handles the issue, though.
> Googling for "firebird transaction logging", I find that Firebird does
> not have a transaction log, but instead relies on a feature called
> "careful write" to maintain consistency, thereby possibly incurring a
> disk seek penalty on commit. Here's a good article explaining how this
> is done:
>
> Firebird for the Database Expert: Episode3 - On disk consistency
> by Ann Harrison
> http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_expert3

THank you Michael for a nice summary of how things work. Not really
anything new to me though.

I still wonder how to configure a FB system to maximize transaction
throughput, on a given hardware setup.

Link to relevant docs, how-to:s, previous discussion threads etc are
also welcome.

Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64