pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Xeon vs Opteron - tests and questions
5+ messages / 3 participants
[nested] [flat]

* Xeon vs Opteron - tests and questions
@ 2005-11-09 14:26 Marcin Giedz <marcin.giedz@eulerhermes.pl>
  2005-11-09 18:15 ` Re: Xeon vs Opteron - tests and questions Jim C. Nasby <jnasby@pervasive.com>
  2005-11-09 19:19 ` Re: Xeon vs Opteron - tests and questions Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 2 replies; 5+ messages in thread

From: Marcin Giedz @ 2005-11-09 14:26 UTC (permalink / raw)
  To: pgsql-admin

Hello.


I made some test comparing postgresql 8.0.4 based on two servers. 

Here is a link:
http://85.128.68.44/


From my point of view it seems like:
	- with opteron I found that it works very FAST periodicaly, why??? Maybe I 
did something wrong or.....
	- xeon seems to work almost all time on the same level but has much less 
performance than opteron. Is it normal?

Did anyone has similar tests/results?

BR,
Marcin



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Xeon vs Opteron - tests and questions
  2005-11-09 14:26 Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
@ 2005-11-09 18:15 ` Jim C. Nasby <jnasby@pervasive.com>
  2005-11-09 18:49   ` Re: Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
  1 sibling, 1 reply; 5+ messages in thread

From: Jim C. Nasby @ 2005-11-09 18:15 UTC (permalink / raw)
  To: Marcin Giedz <marcin.giedz@eulerhermes.pl>; +Cc: pgsql-admin

That link isn't working for me, but if you're seeing 'spikey'
performance I'd bet that you need to change the bg_writer settings to
make it more aggressive, especially if you're seeing performance drops
every 5 minutes (assuming default checkpoint settings).

You might also want to up wal_buffers and maybe checkpoint_segments.

On Wed, Nov 09, 2005 at 03:26:51PM +0100, Marcin Giedz wrote:
> Hello.
> 
> 
> I made some test comparing postgresql 8.0.4 based on two servers. 
> 
> Here is a link:
> http://85.128.68.44/
> 
> 
> From my point of view it seems like:
> 	- with opteron I found that it works very FAST periodicaly, why??? Maybe I 
> did something wrong or.....
> 	- xeon seems to work almost all time on the same level but has much less 
> performance than opteron. Is it normal?
> 
> Did anyone has similar tests/results?
> 
> BR,
> Marcin
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Xeon vs Opteron - tests and questions
  2005-11-09 14:26 Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
  2005-11-09 18:15 ` Re: Xeon vs Opteron - tests and questions Jim C. Nasby <jnasby@pervasive.com>
@ 2005-11-09 18:49   ` Marcin Giedz <marcin.giedz@eulerhermes.pl>
  2005-11-09 20:29     ` Re: Xeon vs Opteron - tests and questions Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Marcin Giedz @ 2005-11-09 18:49 UTC (permalink / raw)
  To: Jim C. Nasby <jnasby@pervasive.com>; +Cc: pgsql-admin

Jim C. Nasby napisaƂ(a):

>That link isn't working for me, 
>

Uppssss sorry... now it should work OK.

>but if you're seeing 'spikey'
>performance I'd bet that you need to change the bg_writer settings to
>make it more aggressive, especially if you're seeing performance drops
>Every 5 minutes (assuming default checkpoint settings).
>  
>
>You might also want to up wal_buffers and maybe checkpoint_segments.
>  
>

OK many thanks, I will check.


>On Wed, Nov 09, 2005 at 03:26:51PM +0100, Marcin Giedz wrote:
>  
>
>>Hello.
>>
>>
>>I made some test comparing postgresql 8.0.4 based on two servers. 
>>
>>Here is a link:
>>http://85.128.68.44/
>>
>>
>>From my point of view it seems like:
>>	- with opteron I found that it works very FAST periodicaly, why??? Maybe I 
>>did something wrong or.....
>>	- xeon seems to work almost all time on the same level but has much less 
>>performance than opteron. Is it normal?
>>
>>Did anyone has similar tests/results?
>>
>>BR,
>>Marcin
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 9: In versions below 8.0, the planner will ignore your desire to
>>       choose an index scan if your joining column's datatypes do not
>>       match
>>
>>    
>>
>
>  
>




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Xeon vs Opteron - tests and questions
  2005-11-09 14:26 Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
  2005-11-09 18:15 ` Re: Xeon vs Opteron - tests and questions Jim C. Nasby <jnasby@pervasive.com>
  2005-11-09 18:49   ` Re: Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
@ 2005-11-09 20:29     ` Jim C. Nasby <jnasby@pervasive.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Jim C. Nasby @ 2005-11-09 20:29 UTC (permalink / raw)
  To: Marcin Giedz <marcin.giedz@eulerhermes.pl>; +Cc: pgsql-admin

The first graph certainly looks like a checkpointing issue.

On Wed, Nov 09, 2005 at 07:49:23PM +0100, Marcin Giedz wrote:
> Jim C. Nasby napisa??(a):
> 
> >That link isn't working for me, 
> >
> 
> Uppssss sorry... now it should work OK.
> 
> >but if you're seeing 'spikey'
> >performance I'd bet that you need to change the bg_writer settings to
> >make it more aggressive, especially if you're seeing performance drops
> >Every 5 minutes (assuming default checkpoint settings).
> > 
> >
> >You might also want to up wal_buffers and maybe checkpoint_segments.
> > 
> >
> 
> OK many thanks, I will check.
> 
> 
> >On Wed, Nov 09, 2005 at 03:26:51PM +0100, Marcin Giedz wrote:
> > 
> >
> >>Hello.
> >>
> >>
> >>I made some test comparing postgresql 8.0.4 based on two servers. 
> >>
> >>Here is a link:
> >>http://85.128.68.44/
> >>
> >>
> >>From my point of view it seems like:
> >>	- with opteron I found that it works very FAST periodicaly, why??? 
> >>	Maybe I did something wrong or.....
> >>	- xeon seems to work almost all time on the same level but has much 
> >>	less performance than opteron. Is it normal?
> >>
> >>Did anyone has similar tests/results?
> >>
> >>BR,
> >>Marcin
> >>
> >>---------------------------(end of broadcast)---------------------------
> >>TIP 9: In versions below 8.0, the planner will ignore your desire to
> >>      choose an index scan if your joining column's datatypes do not
> >>      match
> >>
> >>   
> >>
> >
> > 
> >
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Xeon vs Opteron - tests and questions
  2005-11-09 14:26 Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
@ 2005-11-09 19:19 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 5+ messages in thread

From: Tom Lane @ 2005-11-09 19:19 UTC (permalink / raw)
  To: Marcin Giedz <marcin.giedz@eulerhermes.pl>; +Cc: pgsql-admin

Marcin Giedz <marcin.giedz@eulerhermes.pl> writes:
> I made some test comparing postgresql 8.0.4 based on two servers. 
> Here is a link:
> http://85.128.68.44/

This is pretty nearly an ideal example of how NOT to use pg_bench :-(

In the first place, don't use a number of clients (-c) much exceeding
the scale factor (-s).  If you do, then almost all you are measuring is
the effects of update contention.  There are only scale-factor rows in
the branches table, and every pgbench transaction wants to update one of
the branches rows, so with -c 100 and -s 20 there are on average going
to be 5 transactions simultaneously trying to modify the same branches
row.  4 of them are going to be waiting.  Does that really correspond
to a real-world situation that you want to optimize?

In the second place, you need a run length considerably longer than
-t 100 to avoid getting swamped by noise of startup/shutdown overhead.
I usually use at least -t 1000 if I want repeatable numbers.

BTW, PG 8.1 will probably do better than 8.0 on multi-CPU hardware.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2005-11-09 20:29 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-11-09 14:26 Xeon vs Opteron - tests and questions Marcin Giedz <marcin.giedz@eulerhermes.pl>
2005-11-09 18:15 ` Jim C. Nasby <jnasby@pervasive.com>
2005-11-09 18:49   ` Marcin Giedz <marcin.giedz@eulerhermes.pl>
2005-11-09 20:29     ` Jim C. Nasby <jnasby@pervasive.com>
2005-11-09 19:19 ` Tom Lane <tgl@sss.pgh.pa.us>

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