Re: New to PostgreSQL, performance considerations - Mailing list pgsql-performance

From Daniel van Ham Colchete
Subject Re: New to PostgreSQL, performance considerations
Date
Msg-id 8a0c7af10612120858g1b1b4454x518a3ed609324627@mail.gmail.com
Whole thread Raw
In response to Re: New to PostgreSQL, performance considerations  (Michael Stone <mstone+postgres@mathom.us>)
Responses Re: New to PostgreSQL, performance considerations  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: New to PostgreSQL, performance considerations  ("Daniel van Ham Colchete" <daniel.colchete@gmail.com>)
Re: New to PostgreSQL, performance considerations  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-performance
Mike,

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.
And I'm testing with my fsync turned off.

Maybe if you lower your -t rate you are going to see this improvement.

Best regards,
Daniel

On 12/12/06, Michael Stone <mstone+postgres@mathom.us> wrote:
> On Tue, Dec 12, 2006 at 07:10:34AM -0200, Daniel van Ham Colchete wrote:
> >are you using "-mtune/-mcpu" or "-march" with GCC?
>
> I used exactly the options you said you used.
>
> >Witch GCC version? Are you working with a 32bits OS or 64bits?
>
> 3.3.5; 32
>
> Mike Stone
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

pgsql-performance by date:

Previous
From: David Boreham
Date:
Subject: Re: Low throughput of binary inserts from windows to linux
Next
From: Tom Lane
Date:
Subject: Re: New to PostgreSQL, performance considerations