At 10:04 PM 17/02/2005 +0000, you wrote:

>Firebird 2.0 Alpha displays the same characteristics as FB 1.5.2.
>Give it a big ass (no I'm not from TX) query on a large database and
>you can see FB has pegged the CPU at 100%. Unlike SQL Server there is
>no way to limit the amount of CPU FB consumes, so all other
>applications on the same CPU/machine starve.
>
>We have a multithreaded application that serves both the internet and
>local workstations. Firebird's current lack of SMP and Hyperthreading
>support as well as CPU throttling problems are forcing management to
>contemplate a major port to SQL Server 2000/2005.

Why not use the Classic server? That will take five minutes (uninstall
Superserver, install Classic) and invlove no changes whatsoever to
databases or your applications.

>When will Firebird be available with SMP or HT support?

Date and time - not known. It is not happening in Firebird 2. It is to
happen in the merger of Firebird 2 and Vulcan. Because several hot
architectural issues concerning that merger are currently under discussion,
we don't have an estimate yet of when Firebird 3 alphas will begin to
appear. (Actually, we still have the first Firebird 2 alpha poised for
release currently).

Vulcan's fine-graining threading works well with both SMP and HT on
Windows/AMD. As to what the solution will be to the HT issues on
Windows/Intel, that's still an unknown.

./heLen