Ehm,

> Hi, all. I am running some performance tests against Firebird, and to
> be honest, it really stinks. For a single client I am getting only
> around 10 TPS. I am sure I must be doing something wrong.
>
> First, let me be clear, I don't want to do a test with write-through
> turned off, because it is crucial that data is guaranteed to be there
> if Firebird goes down.

>"Writing to disk after a commit is not acceptable for my application."

What does that mean?

> But the other thing that appears to be happening is with more than one
> client, I immediately get deadlocks.
>
> Is there a way to configure Firebird to improve its overall
> performance without turning off write-through? Is there a way to get
> rid of the deadlocks?

It depends - deadlocks are your friend, not your enemy.

With regards,

Martijn Tonies
Database Workbench - the developer tool for InterBase & Firebird
Upscene Productions
http://www.upscene.com

See you at the First European Firebird Conference in May in Fulda, Germany
http://www.firebird-conference.com