* Mike Galbraith <efault@gmx.de> wrote:

quoted text
> > > With that patch, pgsql+oltp scales perfectly.
> > 
> > hm, tempting.
> 
> I disagree.  Postgres's scaling problem is trivially corrected by 
> twiddling knobs (or whatnot). [...]

okay, then we need to document it a bit more: what knobs need twiddling 
to make it scale perfectly?

quoted text
> [...]  With that patch, you can't twiddle mysql throughput back, or 
> disk intensive loads for that matter.  You can tweak the preempt 
> number, but it has nothing to do with lag, so anybody can preempt 
> anybody else as you turn the knob toward zero.  Chaos.

okay, convinced.

quoted text
> > Have you tried to hack/fix pgsql to do proper wakeups?
> 
> No, I tried to build without spinlocks to verify, but build croaked. 
> Never went back to slogging through the code.

if it falls back to IPC semaphores that's a bad trade from a performance 
POV. The best would be if it used proper futexes (i.e. pthread_mutex() 
and friends) not some home-grown user-space spinlock thing.

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/