Subject | classic vs superserver |
---|---|
Author | rayholme |
Post date | 2005-03-20T13:56:43Z |
I have tested an application which should normally be perfect for the
super server, but the conversion process is long and arduous with lots
of data manipulation.
The 1.5.2 Superserver on Linux (2 cpu host - cpuaffinity set to 1 even
though this seems to be a windoze only setting) runs about 1/4th the
speed of the classic 1.5.2 on the same machine. The CPU load shows at
95-99% on the superserver (one cpu of course) whereas the classic
runs using perhaps 5% of the cpu. The speed difference is not
accountable to just IPC traffic (at worst that should be 25% hit here
IMHO) .
Is there anything I can do to force the Linux box to stay on one cpu)?
The performance of the SS is akin to IB 6.01 running on my Sun -
95-99% cpu utilization during the conversion is normal and it runs
abominally slow there too.
I highly suspect the cpus are exchanging the server frequently, but
perhaps that is not the real reason. ???????
;={
super server, but the conversion process is long and arduous with lots
of data manipulation.
The 1.5.2 Superserver on Linux (2 cpu host - cpuaffinity set to 1 even
though this seems to be a windoze only setting) runs about 1/4th the
speed of the classic 1.5.2 on the same machine. The CPU load shows at
95-99% on the superserver (one cpu of course) whereas the classic
runs using perhaps 5% of the cpu. The speed difference is not
accountable to just IPC traffic (at worst that should be 25% hit here
IMHO) .
Is there anything I can do to force the Linux box to stay on one cpu)?
The performance of the SS is akin to IB 6.01 running on my Sun -
95-99% cpu utilization during the conversion is normal and it runs
abominally slow there too.
I highly suspect the cpus are exchanging the server frequently, but
perhaps that is not the real reason. ???????
;={