Skip site navigation (1) Skip section navigation (2)

Re: Tablespaces

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>,"Alex J(dot) Avriette" <alex(at)posixnap(dot)net>
Cc: "Dennis Bjorklund" <db(at)zigo(dot)dhs(dot)org>,<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Tablespaces
Date: 2004-02-27 11:39:06
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184CFF2@m0114.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> I do not intend to undertake raw disk tablespaces for 7.5. I'd be
> interested if anyone could provide some real world benchmarking of file
> system vs. raw disk. Postgres benefits a lot from kernel file system cache
> at the moment.

Yes, and don't forget that pg also relys on the OS for grouping and
sorting the physical writes and doing readahead where appropriate.

The use of raw disks is usually paired with the use of kernel aio.
The difference is said to be up to 30% on Solaris. I can assert, that
it made the difference between a bogged down system and a much better behaved
DB on Sun here.

My experience with kaio on AIX Informix is, that kaio is faster as long as IO
is not the bottleneck (disk 100% busy is the metric to watch, not Mb/s), while
for an IO bound system the Informix builtin IO threads that can be used instead
win. (Since they obviously do better at grouping, sorting and readahead
than the AIX kernel does for kaio)

Overall I think the price and komplexity is too high, especially since there are 
enough platforms where the kernel does a pretty good job at grouping, sorting and 
readahead. Additionally the kernel takes non PostgreSQL IO into account.

Andreas

Responses

pgsql-hackers by date

Next:From: ChadDate: 2004-02-27 12:53:04
Subject: BTrees with record numbers
Previous:From: Shridhar DaithankarDate: 2004-02-27 10:52:33
Subject: Re: Thread safe connection-name mapping in ECPG. Is it

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group