Received: from localhost (maia-3.hub.org [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id 46D559FA1DE
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 12 Dec 2006 13:32:39 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024)
	with ESMTP id 14043-06 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Tue, 12 Dec 2006 13:32:33 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id C81219FA173
	for <pgsql-performance@postgresql.org>;
	Tue, 12 Dec 2006 13:32:33 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kBCHWWGM005203;
	Tue, 12 Dec 2006 12:32:32 -0500 (EST)
To: "Daniel van Ham Colchete" <daniel.colchete@gmail.com>
cc: pgsql-performance@postgresql.org
Subject: Re: New to PostgreSQL, performance considerations 
In-reply-to: <8a0c7af10612120858g1b1b4454x518a3ed609324627@mail.gmail.com> 
References: <60psaq5t94.fsf@dba2.int.libertyrms.com>
	<20061211173105.GH16692@mathom.us>
	<E1Gtplp-0004Ka-GM@elasmtp-junco.atl.sa.earthlink.net>
	<20061211184726.GI16692@mathom.us>
	<E1GtrB8-0005rw-Iu@elasmtp-kukur.atl.sa.earthlink.net>
	<457DA782.3060506@modgraph-usa.com>
	<8a0c7af10612111422x6bdcc0c2p7cbfeb5a7b0e0374@mail.gmail.com>
	<20061212013706.GM16692@mathom.us>
	<8a0c7af10612120110v34f7d3c3p6d872efabf97b922@mail.gmail.com>
	<20061212123131.GQ16692@mathom.us>
	<8a0c7af10612120858g1b1b4454x518a3ed609324627@mail.gmail.com>
Comments: In-reply-to "Daniel van Ham Colchete" <daniel.colchete@gmail.com>
	message dated "Tue, 12 Dec 2006 14:58:34 -0200"
Date: Tue, 12 Dec 2006 12:32:31 -0500
Message-ID: <5202.1165944751@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200612/305
X-Sequence-Number: 22361

"Daniel van Ham Colchete" <daniel.colchete@gmail.com> writes:
> I'm making some other tests here at another hardware (also Gentoo). I
> found out that PostgreSQL stops for a while if I change the -t
> parameter on bgbench from 600 to 1000 and I have ~150 tps instead of
> ~950tps.

> I don't know why PostgreSQL stoped, but it was longer than 5 seconds
> and my disk IO was comsuming 100% of my CPU time during this period.

Checkpoint?

			regards, tom lane