Not exactly, I think.
It said that postgresql "Add code to detect an SMP machine and handle
spinlocks accordingly", so it is an issue of spinlock handling, not the distribution
of execution tree.
In SMP enviorment, when using spinlock, when we fail to get the spin lock a
Li YueXin <[EMAIL PROTECTED]> writes:
>I found postgresql running on the multi CPU machine doesn't have
>better performance than single CPU machine. Can you explain the
>reason?
That's a rather sweeping statement to make without offering any
evidence, I should think.
If you gave deta
On Tue, 2003-09-23 at 22:45, Li YueXin wrote:
> I found postgresql running on the multi CPU machine doesn't have
> better performance than single CPU machine. Can you explain the
> reason?
In addition to what Christopher Browne suggests, keep in mind that
PostgreSQL spawns a separate Unix process
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Li YueXin) would write:
> I found postgresql running on the multi CPU machine doesn't have
> better performance than single CPU machine. Can you explain the
> reason? And how to resolve the problem?
The classic reason for this is that if y
I found postgresql running on the multi CPU machine doesn't have better
performance than single CPU machine. Can you explain the reason? And how to resolve
the problem?
In the Todo list, I read the below message:
Add code to detect an SMP machine and handle spinlocks accordingly
from d