Re: [PERFORM] Disk configuration

2005-01-20 Thread Alex Turner
2:53 AM > To: Benjamin Wragg > Cc: pgsql-performance@postgresql.org > Subject: Re: [PERFORM] Disk configuration > > The primary goal is to reduce the number of seeks a disk or array has to > perform. Serial write throughput is much higher than random write > throughput. If y

Re: [PERFORM] Disk configuration

2005-01-19 Thread Benjamin Wragg
, 20 January 2005 2:53 AM To: Benjamin Wragg Cc: pgsql-performance@postgresql.org Subject: Re: [PERFORM] Disk configuration The primary goal is to reduce the number of seeks a disk or array has to perform. Serial write throughput is much higher than random write throughput. If you are performing

Re: [PERFORM] Disk configuration

2005-01-19 Thread Alex Turner
The primary goal is to reduce the number of seeks a disk or array has to perform. Serial write throughput is much higher than random write throughput. If you are performing very high volume throughput on a server that is doing multiple things, then it maybe advisable to have one partition for OS,

Re: [PERFORM] Disk configuration

2005-01-18 Thread Josh Berkus
Benjamin, > I just wanted to bounce off the list the best way to configure disks for a > postgresql server. My gut feeling is as follows: > > Keep the OS and postgresql install on seperate disks to the postgresql > /data directory? > Is a single hard disk drive acceptable for the OS and postgresql

[PERFORM] Disk configuration

2005-01-18 Thread Benjamin Wragg
I just wanted to bounce off the list the best way to configure disks for a postgresql server. My gut feeling is as follows:   Keep the OS and postgresql install on seperate disks to the postgresql /data directory? Is a single hard disk drive acceptable for the OS and postgresql program, or