new group commit behavior not helping? - Mailing list pgsql-hackers

From Jeff Janes
Subject new group commit behavior not helping?
Date
Msg-id CAMkU=1xGw7P2t8c-TCMErbn6R5pNR+q1BVNs-SiFeOcGg2eLSA@mail.gmail.com
Whole thread Raw
In response to new group commit behavior not helping?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: new group commit behavior not helping?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
<br /><br />On Saturday, March 31, 2012, Robert Haas <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>wrote:<br />> Hoping to demonstrate the wonders of
ournew group commit code, I ran<br />> some benchmarks on the IBM POWER7 machine with synchronous_commit =<br />
>on.  But, it didn't come out much better than 9.1.  <br /><br />Where I would expect (and have seen) much
improvementis where #clients >> #CPU.  Or "cores", whatever the term of art is.<br /><br />Of course I've mostly
seenthis where CPU=1<br /><br />It looks like in your case tps was still scaling with clients when you gave up, so
clientswas probably too small.<br /><br />Jeff  

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: measuring lwlock-related latency spikes
Next
From: Robert Haas
Date:
Subject: Re: new group commit behavior not helping?