Subject Re: SortMemBlockSize/SortMemUpperLimit settings
Author rogerpullen
Hi - thanks for that - this has prompted a new question here - we
have the opportunity to purchase a new server and if we were to run
in classic mode would there be any advantage in going for a dual
processor option?



--- In, "Leyne, Sean" <Sean@...>
> Roger,
> > FB 1.5 on a W2003 server with 2GIG RAM - we are having performance
> > issues and am wondering if there is their any benefit of
> the
> > SortMemBlockSize or SortMemUpperLimit parameters in
firebird.conf. I
> > have read the "book" but want to understand the implications a bit
> > better . We normally have about 70 user logged on and believe it
> > excessive reporting that is the culprit
> The real source of your performance problem is the fact that
> engine (in FB v1.x and 2.0 -- FB v2.1 has had more work done on the
> scheduler) does a lousy (v1.x) or poor (v2.0) job of "time-slicing"
> between a larger number active connections.
> You should investigate the Classic engine, it is:
> - much fairer in responding to requests from multiple connections
> - the only current solution which provides any SMP (multi-processor)
> support
> Sean
> P.S. Please remember to change the database cache settings when
> Classic (vs. SuperServer)
> Sean