pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: James Thornton <james@jamesthornton.com>
To: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Recommended File System Configuration
Date: Tue, 04 May 2004 14:38:47 -0500
Message-ID: <4097F147.6050000@jamesthornton.com> (raw)
In-Reply-To: <60zn8pcvp2.fsf@dev6.int.libertyrms.info>
References: <4094AD20.6090707@jamesthornton.com>
	<60zn8pcvp2.fsf@dev6.int.libertyrms.info>

Chris Browne wrote:

> The results have not been totally conclusive...
> 
>  - Several have found JFS to be a bit faster than anything else on
>    Linux, but some data loss problems have been experienced;
> 
>  - ext2 has the significant demerit that with big filesystems, fsck
>    will "take forever" to run;
> 
>  - ext3 appears to be the slowest option out there, and there are some
>    stories of filesystem corruption;


In an Oracle paper entitled Tuning an "Oracle8i Database Running Linux" 
(http://otn.oracle.com/oramag/webcolumns/2002/techarticles/scalzo_linux02.html), 
Dr. Bert Scalzo says, "The trouble with these tests-for example, Bonnie, 
Bonnie++, Dbench, Iobench, Iozone, Mongo, and Postmark-is that they are 
basic file system throughput tests, so their results generally do not 
pertain in any meaningful fashion to the way relational database systems 
access data files." Instead he suggests users benchmarking filesystems 
for database applications should use these two well-known and widely 
accepted database benchmarks:

AS3AP (http://www.benchmarkresources.com/handbook/5.html): a scalable, 
portable ANSI SQL relational database benchmark that provides a 
comprehensive set of tests of database-processing power; has built-in 
scalability and portability for testing a broad range of systems; 
minimizes human effort in implementing and running benchmark tests; and 
provides a uniform, metric, straightforward interpretation of the results.

TPC-C (http://www.tpc.org/): an online transaction processing (OLTP) 
benchmark that involves a mix of five concurrent transactions of various 
types and either executes completely online or queries for deferred 
execution. The database comprises nine types of tables, having a wide 
range of record and population sizes. This benchmark measures the number 
of transactions per second.

I encourage you to read the paper -- Dr. Scalzo's results will surprise 
you; however, while he benchmarked ext2, ext3, ReiserFS, JFS, and RAW, 
he did not include XFS.

SGI and IBM did a more detailed study on Linux filesystem performance, 
which included XFS, ext2, ext3 (various modes), ReiserFS, and JRS, and 
the results are presented in a paper entitled "Filesystem Performance 
and Scalability in Linux 2.4.17" 
(http://oss.sgi.com/projects/xfs/papers/filesystem-perf-tm.pdf). This 
paper goes over the details on how to properly conduct a filesystem 
benchmark and addresses scaling and load more so than Dr. Scalzo's tests.

For further study, I have compiled a list of Linux filesystem resources 
at: http://jamesthornton.com/hotlist/linux-filesystems/.

-- 

  James Thornton
______________________________________________________
Internet Business Consultant, http://jamesthornton.com




view thread (3+ messages)

Message-ID: <4097F147.6050000@jamesthornton.com>
Permalink:  ../4097F147.6050000@jamesthornton.com/
Also on:    postgresql.org/message-id/4097F147.6050000@jamesthornton.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: james@jamesthornton.com, cbbrowne@acm.org
  Subject: Re: Recommended File System Configuration
  In-Reply-To: <4097F147.6050000@jamesthornton.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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