On Thu, 4 Jun 2009, Mark Mielke wrote:
At it's very simplest, this is the difference between "wake one thread" (which is then responsible for waking the next thread) vs "wake all threads"....Any system which actually wakes all threads will probably exhibit scaling limitations.
The prototype patch we got from Jignesh improved his specific workload by waking more waiting processes than were being notified in the current code. The bottleneck that's been best examined so far at high client counts is not because of too much waking, it's caused by not enough.
-- * Greg Smith gsmith@xxxxxxxxxxxxx http://www.gregsmith.com Baltimore, MD -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
