Firebird – 1 terabyte database tests and performance report

We have made 1 terabyte database test with Firebird 2.1. Read more. Questions?

Summary
In this experiment Firebird shows the following results

Undoubted ability to handle big databases. We are pretty sure that it’s possible to create and use 32 Tb database on appropriate hardware, and Firebird will show the same high performance as it shows for smaller databases (i.e., 1Tb and below).

Good scalability and amazingly small footprint. 1Tb database was created at usual desktop computer and, more important, it can be used to perform general queries: if you don’t fetch millions of records, query’s speed is the same as it is for moderate size databases (10-15Gb).

Firebird – query to show which fields in your database are not based on a domain

Our strategy is that in all of our InterBase and Firebird databases, the column definitions are based on domains.

But some of our databases do not have that for all columns (usually because we got involved later in the development cycle).

When you forget to define a column based on a domain, then both InterBase and Firebird will create a new system domain on the fly that starts with ‘RDB$’.
So if you forget, you get a new system domain for every column!

The below query will list those columns.

Cache flushes to disk and Firebird

Paul Beach wrote on his Blog
The following fragment of a message appeared on the Firebird development list. As the question and answer are interesting, I thought I would put it on the blog.

“If I want to make cache flushes to disk very rare, do I set MaxUnflushedWrites & MaxUnflushedWriteTime to -1 or to some large value?
What other settings adjustments can make table flushes to disk more rare?
Is there any combination of settings that will keep the entire db in cache and never flush it to disk?”

1 22 23 24 25 26 48