From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Paweł Gruszczyński <pawel.gruszczynski@inea.com.pl>
Cc: pgsql-performance@postgresql.org
Subject: Re: What`s wrong with JFS configuration?
Date: Wed, 25 Apr 2007 09:54:12 +0100
Message-ID: <462F1734.3080705@enterprisedb.com> (raw)
In-Reply-To: <462EFA63.1030306@inea.com.pl>
References: <462EFA63.1030306@inea.com.pl>
Paweł Gruszczyński wrote:
> To test I use pgBench with default database schema, run for 25, 50, 75
> users at one time. Every test I run 5 time to take average.
> Unfortunetly my result shows that ext is fastest, ext3 and jfs are very
> simillar. I can understand that ext2 without jurnaling is faster than
> ext3, it is said that jfs is 40 - 60% faster. I cant see the difference.
> Part of My results: (transaction type | scaling factor | num of clients
> | tpl | num on transactions | tps including connection time | tps
> excliding connection time)
>
> EXT2:
>
> TPC-B (sort of),50,75,13,975|975,338.286682,358.855582
> ...
>
> Can anyone tell me what`s wrong with my test? Or maybe it is normal?
With a scaling factor of 50, your database size is ~ 1 GB, which fits
comfortably in your RAM. You're not exercising your drives or filesystem
much. Assuming you haven't disabled fsync, the performance of that test
is bound by the speed your drives can flush WAL commit records to disk.
I wouldn't expect the filesystem to make a big difference anyway, but
you'll see..
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
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: heikki@enterprisedb.com, pawel.gruszczynski@inea.com.pl
Subject: Re: What`s wrong with JFS configuration?
In-Reply-To: <462F1734.3080705@enterprisedb.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