Subject | Re: [firebird-support] New User Question |
---|---|
Author | Helen Borrie |
Post date | 2006-11-29T05:22:43Z |
At 02:50 PM 29/11/2006, you wrote:
If you want to check the bugfixes in Firebird since it was IB6, see
the appropriate sections in the release notes for Firebird versions
1.0.3, 1.5.3 and 2.0. They run into the high hundreds, all up.
If you want to know whether Firebird Superserver supports SMP, the
answer is No. But from 1.5 onward, you don't (and must not) use
IBAffinity to set the affinity, you use a setting in
firebird.conf. Single-CPU affinity is set by default (to CPU 0) and
you can change it to a different single CPU by setting a bitmask
(instructions in both the 1.5 release notes and firebird.conf itself)
for the CPUAffinityMask parameter.
On Windows you also have the option of Firebird Classic from v.1.5
onward. You can use all your CPUs with Classic and the
CPUAffinityMask is irrelevant. Again, read the release notes.
./heLen
>We have been using IB 6.0.2.0 for about 5 years and are beginning to useFor what purpose? I mean, to compare what?
>the new dual core hyperthreaded processor boards on which it will not
>run without using the IBAffinity program. Is there a place where we can
>see a comparison of IB and Firebird?
If you want to check the bugfixes in Firebird since it was IB6, see
the appropriate sections in the release notes for Firebird versions
1.0.3, 1.5.3 and 2.0. They run into the high hundreds, all up.
If you want to know whether Firebird Superserver supports SMP, the
answer is No. But from 1.5 onward, you don't (and must not) use
IBAffinity to set the affinity, you use a setting in
firebird.conf. Single-CPU affinity is set by default (to CPU 0) and
you can change it to a different single CPU by setting a bitmask
(instructions in both the 1.5 release notes and firebird.conf itself)
for the CPUAffinityMask parameter.
On Windows you also have the option of Firebird Classic from v.1.5
onward. You can use all your CPUs with Classic and the
CPUAffinityMask is irrelevant. Again, read the release notes.
./heLen