Subject RE: [firebird-support] Re: FB 1.5 vs. Win2003 + Xeon
Author Nigel Weeks
This issue gets addressed at least every two days.

Don't use SuperServer on multiple CPU's, either HyperThreaded, Dual Core, or
Windows's CPU scheduling is broken - it happens with ANY single-process,
high-cpu-demand software.

Lock it to one CPU, or use the right tool for SMP machines - Classic Server.


-----Original Message-----
[]On Behalf Of Tim
Sent: Wednesday, 7 June 2006 4:03 PM
Subject: Re: [firebird-support] Re: FB 1.5 vs. Win2003 + Xeon

Maybe Windows gets confused? A known issue (with databases -
documented somewhere in the old Interbase docs) is that Windows tries
load balancing. So what happens is that the DB usage (and hence CPU
usage) goes up. Windows notices, and tries to swap processors to
balance the load. Because of the nature of db operations, the load on
the new processor goes up. So windows notices. And swaps processors
to balance the load .....

and so on and so forth. :)

(I am sure others can explain it much better than I can)

The solution (which we have done on all our installations - about 800
of them) is to disable hyperthreading. I wonder if maybe the same
issue could be happening with dual core processors?



At 07:47 07/06/2006, you wrote:

>I am not sure, but I think I have a similar problem.
>A customer runs FB SS on a Windows 2003 Dual Core Server.
>Sometimes (a few days after booting the server) FB slows down
>dramatically. Processor usage goes up to 50%.
>A restart of the FB service doesn't help. I have to restart the
>Windows 2003 server, to solve the problem. This is very awkward,
>because the customer works in 3 shifts and there is allways anyone
>connected to the database.
>What could be the reason for this problem? Are there any knowen issues
>on this?
>What could I try to solve this problem?
>Kind regards

[Non-text portions of this message have been removed]

__________ NOD32 1.1582 (20060606) Information __________

This message was checked by NOD32 antivirus system.

[Non-text portions of this message have been removed]