pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Data and logs on different physical drives - advantage?
3+ messages / 2 participants
[nested] [flat]

* Data and logs on different physical drives - advantage?
@ 2005-10-10 11:41  Weber, Johann (ISS Kassel) <jweber@iss.net>
  0 siblings, 1 reply; 3+ messages in thread

From: Weber, Johann (ISS Kassel) @ 2005-10-10 11:41 UTC (permalink / raw)
  To: pgsql-admin

I learned for other database systems, that it is an advantage to have
database on one physical drive and transaction logs on a different
physical drive, as this should minimize seeks on the hard-disks.
 
Is this true for PostgreSQL (V 8.0 on ReadHat)? My tests do not show any
speed gained when placing pg_clog and pg_xlog on a different drive.
 

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

* Re: Data and logs on different physical drives - advantage?
@ 2005-10-10 14:34  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Weber, Johann (ISS Kassel) <jweber@iss.net>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2005-10-10 14:34 UTC (permalink / raw)
  To: Weber, Johann (ISS Kassel) <jweber@iss.net>; +Cc: pgsql-admin

"Weber, Johann (ISS Kassel)" <jweber@iss.net> writes:
> Is this true for PostgreSQL (V 8.0 on ReadHat)? My tests do not show any
> speed gained when placing pg_clog and pg_xlog on a different drive.

The conventional wisdom is that it's a win to have pg_xlog on a drive by
itself.  The above is not that.  pg_clog is more in the nature of data,
and in any case you lose the advantage as soon as the drive handling
pg_xlog has to move the head away from the current xlog file.

Whether any particular test case would show an advantage is another
question of course.  In a heavy-write scenario I would think you could
probably measure a win.

			regards, tom lane



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

* Re: Data and logs on different physical drives - advantage?
@ 2005-10-10 14:40  Weber, Johann (ISS Kassel) <jweber@iss.net>
  0 siblings, 0 replies; 3+ messages in thread

From: Weber, Johann (ISS Kassel) @ 2005-10-10 14:40 UTC (permalink / raw)
  To: pgsql-admin

 Thanks, after playing around a little I found that placing the indices
on a different drive gave a real performance increase in my scenario.
Johann


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Monday, October 10, 2005 4:35 PM
To: Weber, Johann (ISS Kassel)
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Data and logs on different physical drives -
advantage? 

"Weber, Johann (ISS Kassel)" <jweber@iss.net> writes:
> Is this true for PostgreSQL (V 8.0 on ReadHat)? My tests do not show 
> any speed gained when placing pg_clog and pg_xlog on a different
drive.

The conventional wisdom is that it's a win to have pg_xlog on a drive by
itself.  The above is not that.  pg_clog is more in the nature of data,
and in any case you lose the advantage as soon as the drive handling
pg_xlog has to move the head away from the current xlog file.

Whether any particular test case would show an advantage is another
question of course.  In a heavy-write scenario I would think you could
probably measure a win.

			regards, tom lane





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


end of thread, other threads:[~2005-10-10 14:40 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-10-10 11:41 Data and logs on different physical drives - advantage? Weber, Johann (ISS Kassel) <jweber@iss.net>
2005-10-10 14:34 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-10-10 14:40 Re: Data and logs on different physical drives - advantage? Weber, Johann (ISS Kassel) <jweber@iss.net>

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