Nigel Weeks wrote:

>
>> If you are running a complex query in Superserver, it hurts everyone's
>> performance. The same query on Classic will tie down one of the cores
>> but other queries get a better look in. This has to be weighed up
>> against Superserver having the benefit of a shared cache which can
>> therefore be larger. Because of this, I have noticed very little
>> difference on a dual core box when we look at performance between the
>> two models. What Superserver loses in being tied to 1 CPU it makes up
>> with by more cache hits, but as it scales out to 4, 8 and 16 core
>> boxes, classic pulls a long way ahead in our experience.
>>
>
> I just have to add that a large cache on your SCSI controller makes a HUGE
> difference to Classic - even if it's smaller than the DB size itself, having
> index pages and recent records in CACHE is nice...
>
> N.
>

And even the file system cache would play nice, when using CS the "best
bet" is to leave the cache size at the default level (75 pages) and let
the file system perform the cache between the process.

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br