pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: John Rouillard <rouilj@renesys.com>
To: Jeff <threshar@torgo.dyndns-server.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Using pgiosim realistically
Date: Tue, 17 May 2011 17:35:19 +0000
Message-ID: <20110517173519.GH27218@renesys.com> (raw)
In-Reply-To: <CF55DDA4-5AC1-47AE-84E8-08868D1BF494@torgo.978.org>
References: <20110513210941.GX27218@renesys.com>
	<20110514170702.GC32389@staff-mud-56-27.rice.edu>
	<20110516131730.GA27218@renesys.com>
	<B15C84A0-369F-4F29-B3F3-A85C3107DDBD@torgo.978.org>
	<20110516170636.GB27218@renesys.com>
	<CF55DDA4-5AC1-47AE-84E8-08868D1BF494@torgo.978.org>

On Mon, May 16, 2011 at 01:54:06PM -0400, Jeff wrote:
> Yep - you need multiple threads to get max throughput of your io.

I am running:

   ~/pgiosim -c -b 100G -v -t4 file[0-9]*

Will each thread move 100GB of data? I am seeing:

  158.69%,   4260 read,      0 written, 3407.64kB/sec  425.95 iops

Maybe the completion target percentage is off because of the threads?

-- 
				-- rouilj

John Rouillard       System Administrator
Renesys Corporation  603-244-9084 (cell)  603-643-9300 x 111



view thread (7+ messages)

Message-ID: <20110517173519.GH27218@renesys.com>
Permalink:  ../20110517173519.GH27218@renesys.com/
Also on:    postgresql.org/message-id/20110517173519.GH27218@renesys.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: rouilj@renesys.com, threshar@torgo.dyndns-server.com
  Subject: Re: Using pgiosim realistically
  In-Reply-To: <20110517173519.GH27218@renesys.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox