Hi Nelson,

It all depends on the number of concurrent connections to the database
server. If you have a huge number of users and have little RAM, then you're
better off with Firebird RC6 Super Server. If you have lots of memory, then
use the Classic Server.
If you have only one user, both architectures are good but with Super Server
you will benefit from the service API.

One important issue to take into consideration. From what I recall with
Linux Kernels, the old kernels (2.2.X) were not very efficient when
executing a complex query that loaded the CPU. The kernel kept moving the
process from one CPU to the other, therefore reducing drastically the
performance. With kernels 2.4 and above, Linux handles those cases in a much
better way.

We have used Firebird 1.0.2 on Redhat 7.0 Dual P3, Firebird 1.0.3 on Redhat
Linux 8.0 (Kernel 2.4.19) Dual Xeons 2.0 GHz, and Firebird 1.5 RC4 on Dual
Xeons without problems. All were classic versions, number of connections
ranging from 12 to 40, Database size from 1.1 GB to 2.4 GB.

One important issue if you use the classic version, remember to fix the
"instances" in xinetd.conf to a higher number if you plan on using the
classic version and have more than 60 connections.

Salim

-----Original Message-----
From: Joao Nelson [mailto:joaonelson@...]
Sent: Monday, October 20, 2003 9:40 PM

Hi, What are configuration for firebird work with 2 cpus? My SO is Linux
RadHat.
Thank you,

Nelson