Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Apr 2007 00:57:54 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        Kevin Way <kevin@insidesystems.net>
Cc:        freebsd-performance@freebsd.org
Subject:   Re: Anyone interested in improving postgresql scaling?
Message-ID:  <20070410045754.GA41769@xor.obsecurity.org>
In-Reply-To: <461B0CD0.8090404@insidesystems.net>
References:  <461B0CD0.8090404@insidesystems.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 10, 2007 at 12:04:32AM -0400, Kevin Way wrote:
> Kris Kennaway wrote:
> >If so, then your task is the following:
> >
> >Make SYSV semaphores less dumb about process wakeups.  Currently
> >whenever the semaphore state changes, all processes sleeping on the
> >semaphore are woken, even if we only have released enough resources
> >for one waiting process to claim.  i.e. there is a thundering herd
> >wakeup situation which destroys performance at high loads.  Fixing
> >this will involve replacing the wakeup() calls with appropriate
> >amounts of wakeup_one().
> Could this cause problem cause a situation where an 8-Core system was=20
> 50-75% slower than an otherwise equivalent 2-Core system?
>=20
> I have a graph of my sysbench/pgsql results here:
>=20
>    http://blog.insidesystems.net/files/sysctl-pgsq-amd64-wtf.png
>=20
> As the graph shows, the 8-core system is about half the speed of the=20
> 2-core system at 2 simultaneous threads, and it decays down to=20
> approximately 1/4 the speed of the 2-core system as the # of threads hits=
 5.
>=20
> All other (non-pgsql, non-sysv) tests came back approximately as=20
> expected, but I'm left wondering if I did something wrong, or if 8 cpus=
=20
> are slower than 2, when it comes to Postgres on currently available FreeB=
SD.

I wouldn't expect 6.2 to have good scaling on 8 cpus for this kind of
benchmark.  Fixing that was what we have been working on for 7.0 (and
basically succeeded).  The most important fixes are already in 7.0
CVS, but a possible merge to 6.x will only happen after a suitably
conservative delay.

Kris

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQFGGxlSWry0BWjoQKURAlzLAJ9Q0F2UTkn64W9LQ8GLkd+ogDySIwCfUS3F
ZIagTRCYOWo6F12ypxTh7BY=
=ey3P
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070410045754.GA41769>