I've set this parameter to 256 to test, still getting the same results. The only way I reliably see a spike in IO at all is on the pgbench initialization (still peaking around 110MB/sec writes), so I'm thinking about playing around with that or duplicating its approach with larger rows and running it from multiple sessions in different initialization databases on the same volume. If I cant push it further using that technique then there must be some dumb bottleneck in config I am overlooking.
On Tue, May 10, 2016 at 3:24 PM, Kevin Grittner <kgrittn@xxxxxxxxx> wrote:
On Tue, May 10, 2016 at 2:02 PM, Mike Broers <mbroers@xxxxxxxxx> wrote:
> If someone has an idea for how to set up pgbench to
> really push the io to prove out ssd potential, or a different
> script/approach that would be awesome.
You might want to play with some large effective_io_concurrency
settings, starting around 256.
http://www.postgresql.org/message-id/CAHyXU0yiVvfQAnR9cyH=HWh1WbLRsioe=mzRJTHwtr=2azsTdQ@xxxxxxxxxxxxxx
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
