Hi! On Mon, May 17, 2004 at 06:04:54PM +0100, Richard Huxton wrote: > [EMAIL PROTECTED] wrote: > > [...] > > In no official capacity whatsoever, welcome aboard.
Thanks ;-) > > There is just one point where I found the documentation lacking any > > description and practical hints (as opposed to all other topics), namely > > that of how to tune a setup for maximum performance regarding the layout of > > partitions on hard-disks and their mount options. > > I'm not a Sun user, so I can't give any OS-specific notes, but in general: > - Don't bypass the filesystem, but feel free to tinker with mount > options if you think it will help Right, raw partitions are too low-level for me these days anyhow... I assume that all postgres partitions can be mounted with noatime? > - If you can put WAL on separate disk(s), all the better. Does that mean only the xlog, or also the clog? As far as I understand, the clog contains some meta-information on the xlog, so presumably it is flushed to disc synchronously together with the xlog? That would mean that they each need a separate disk to prevent one disk having to seek too often...? > - Battery-backed write-cache for your SCSI controller can be a big > performance win I probably won't be able to get such a setup for this project; that's why I am bothering about which disk will be seeking how often. > - Tablespaces _should_ be available in the next release of PG, we'll > know for sure soon. That might make life simpler for you if you do want > to spread your database around by hand, Ok, I think tablespaces are not the important thing - at least for this project of ours. > > What I should add is that reliability is a premium for us, we do not want to > > sacrifice integrity for speed, and that we are tuning for a high commit rate > > of small, simple transactions... > > Make sure the WAL is on fast disks I'd suggest. At a guess that'll be > your bottleneck. > > For more info, your best bet is to check the archives on the > plpgsql-performance list, and then post there. People will probably want > to know more about your database size/number of concurrent > transactions/disk systems etc. Here goes ... we are talking about a database cluster with two tables where things are happening, one is a kind of log that is simply "appended" to and will expect to reach a size of several million entries in the time window that is kept, the other is a persistent backing of application data that will mostly see read-modify-writes of single records. Two writers to the history, one writer to the data table. The volume of data is not very high and RAM is enough... If any more information is required feel free to ask - I would really appreciate getting this disk layout sorted out. Thanks, Colin ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org