Subject | CPU afinity with classic version |
---|---|
Author | Salim Naufal |
Post date | 2002-05-11T20:37:56Z |
On a Redhat 7.2 Linux system, Dual CPU machine, we have installed Firebird
1.0 Classic architecture. When performing a long query or a restore, I have
noticed that the process is being switched from one CPU to the other
indefinitely, therefore reducing the overall performance. I recall that this
was a problem with the superserver architecture and that it was fixed by
integrating the CPU affinity option.
Does anyone have some experience with such a hardware/software
configuration? I though that the classic version of IB would be ideal for
such a scenario (about 15 concurrent users). Will the superserver version of
Firebird yield better results than the classic one?
Any help is appreciated. Thanks
Salim
1.0 Classic architecture. When performing a long query or a restore, I have
noticed that the process is being switched from one CPU to the other
indefinitely, therefore reducing the overall performance. I recall that this
was a problem with the superserver architecture and that it was fixed by
integrating the CPU affinity option.
Does anyone have some experience with such a hardware/software
configuration? I though that the classic version of IB would be ideal for
such a scenario (about 15 concurrent users). Will the superserver version of
Firebird yield better results than the classic one?
Any help is appreciated. Thanks
Salim