Re: JFS fastest filesystem for PostgreSQL?

From: "Dmitri Bichko" <dbichko(at)aveopharma(dot)com>
To: "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: JFS fastest filesystem for PostgreSQL?
Date: 2005-07-14 07:08:41
Message-ID: F18A6F7CF1661F46920F2CF713122FED46CC10@mail.aveo.aveopharma.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I was wondering - have you had a chance to run the same benchmarks on
ReiserFS (ideally both 3 and 4, with notail)?

I'd be quite interested to see how it performs in this situation since
it's my fs of choice for most things.

Thanks,
Dmitri

-----Original Message-----
From: pgsql-performance-owner(at)postgresql(dot)org
[mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of Jeffrey W.
Baker
Sent: Thursday, July 14, 2005 2:34 AM
To: pgsql-performance(at)postgresql(dot)org
Subject: [PERFORM] JFS fastest filesystem for PostgreSQL?

[reposted due to delivery error -jwb]

I just took delivery of a new system, and used the opportunity to
benchmark postgresql 8.0 performance on various filesystems. The system
in question runs Linux 2.6.12, has one CPU and 1GB of system memory, and
5 7200RPM SATA disks attached to an Areca hardware RAID controller
having 128MB of cache. The caches are all write-back.

I ran pgbench with a scale factor of 1000 and a total of 100,000
transactions per run. I varied the number of clients between 10 and
100. It appears from my test JFS is much faster than both ext3 and XFS
for this workload. JFS and XFS were made with the mkfs defaults. ext3
was made with -T largefile4 and -E stride=32. The deadline scheduler
was used for all runs (anticipatory scheduler is much worse).

Here's the result, in transactions per second.

ext3 jfs xfs
-----------------------------
10 Clients 55 81 68
100 Clients 61 100 64
----------------------------

-jwb

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer

Browse pgsql-performance by date

  From Date Subject
Next Message Relaxin 2005-07-14 07:19:34 PostgresSQL vs. Firebird
Previous Message Dennis 2005-07-14 06:54:38 Re: performance problems ... 100 cpu utilization