A huge page buffer and several simultaneous processes

Question

One of our customers has a 35 GB database with average active connections numbering around 70-80. Some tables in the database have more than 10 M records in the table.

Now they bought a new server: 4 * 6 Core = 24 Cores CPU, 48 Gb RAM, 2 RAID-controllers 256 MB cache, with 8 SAS 15K HDDs on each.

64-bit OS

I am wondering what a quick configuration is:

1) FB 2.5 SuperServer with a huge buffer of 8192 * 3,500,000 pages = 29 GB

or

2) FB 2.5 Classic with a small buffer of 1000 pages.

Maybe someone has experienced such an event before and will save me days of work :)

Thanks in advance.

Answer 1

Because there are many processors that I would start with Classic.

But try everything.

Maybe soon 2.5 with superclassics might be great for you.

Answer 2

just dig out the old thread for those who might need it.

We use fb classic 2.5 on 75GB db, the machine is almost the same as described.

SuperServer was ineffective during the tests. Buffers and page resizing only made performance a little less miserable.

We are currently using Classic with xinetd, page size = 16384, page buffers = 5000,

Answer 3

SuperServer will use ONLY ONE PROCESSOR. Since you have 24 cores, the best option is to use Clasic. SuperClasic is not yet ready to scale well in a multi-processor environment.

Answer 4

Definitely go with one of the "classic" architectures.
If you are using Firebird 2.5, check out SuperClassic .

Answer 5

I currently have a client with similar requirements.

The best solution for this case was to install FireclickSQL 2.5 SuperClassic and just leave the small caching settings as default, because if you have free memory (RAM), Windows and Linux are better at caching the database, and Firebird. The caching feature of Firebird is not very fast, so let the OS do it.

In addition, depending on what backup software you use, if it often creates full backups of the firebird database, you can deactivate forced entries in the databases. (just do it if you know what you are doing, and if you know what can happen by deactivating forced recordings).