Yes, I tried classic on the box and it blew away SS performance wise
(not even close for loads). But for the real application, SS is the
better choice. My point is that I want to exclude 2 cpus from the game
(cpuaffinity==1 as documented in windoze but not for Linux ) - I
want SS to stay on one and let JAVA have the other. I believe SS is
killing itself shifting cpus (classic thrashing if you will and then
in the second case mentioned below - classical swap space overload
death is eventually forcing a core dump).

If I clean out trash using gfix -sweep before running the test I am
running, the test runs to end fine.

Thanks.

Ray



--- In firebird-support@yahoogroups.com, Uwe Grauer
<mailinglists@o...> wrote:

> rayholme wrote:
>
> >
> > 1) It would appear that the cpuaffinity setting only works on
> > windoze (as documented) - that is a bloody shame as a 2 cpu Unix or
> > Linux machine could benefit here a lot
> >
> > 2) the SS goes to 99% cpu utilization (and sometimes core dumps)
> > when extreme cleanup and housekeeping is required by a transaction.
> > It's memory utilization goes up and up (ok if enough swap space, core
> > dump if not) - the lack of real memory may be the real reason for the
> > high cpu utilization - it may be swapping like heck.
> >
> If you want to take both cpu's into the game you have to use classic

server.

> Did you try it?
>
> Uwe