On 29/08/2013 16:09, Leyne, Sean wrote:

>
> > > (3) Do these motivations make sense?
> >
> > Yes and no. ;-]
> >
> > Classic does not provide the fastest performance, but it does
> provide the
> > most consistent multi-connection performance. It is currently (v3
> will be
> > changing this) the only engine which truly scales across CPUs.
>
> In re-reading my post, I realize that the above is not as technically
> correct as it should be. I should have written:
>
> Classic does not provide the fastest performance, but it does provide
> the most consistent multi-connection performance. It is currently (v3
> will be changing this) the only engine which is able to use
> multi-cores/CPU to support multiple database connections*
>
> Sean
>
> * Each connection is a dedicated OS process, which the OS is able to
> move to free CPU resource has the load increases.
>

But I thought Superserver used threads? And threads can run on separate
CPUs? (Processes are an address space thing, not a CPU thing.)

--
Tim Ward



[Non-text portions of this message have been removed]