mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Igor A. Valcov" <viaprog@gmail.com>
To: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS filesystem performance drop in kernels 2.6.16+
Date: Fri, 10 Nov 2006 16:16:27 +0300	[thread overview]
Message-ID: <bde600590611100516u7b8ca1bfs74d3cc8b78eb3520@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0611101259490.6068@yvahk01.tjqt.qr>

Below is a simplified version of the test program, and results of
testing different kernels/filesystems/mount options. The results are a
little different from the ones described in the initial post (this
time performance decreased "only" 2 times), but the general tendency
is clearly the same.


============ 2.6.19-rc5-git2 ============

mount -t xfs -o noatime,barrier /dev/sdc1 /mnt/disc

real    16m40.516s
user    0m17.989s
sys    9m36.320s

mount -t xfs -o noatime,nobarrier /dev/sdc1 /mnt/disc

real    15m40.212s
user    0m17.549s
sys    9m29.692s

mount -t ext3 -o noatime /dev/sdc1 /mnt/disc

real    49m44.728s
user    0m27.678s
sys    14m15.689s

============ 2.6.14.6 ============

mount -t xfs -o noatime /dev/sdc1 /mnt/disc

real    9m58.974s
user    0m17.373s
sys    8m4.850s

mount -t ext3 -o noatime /dev/sdc1 /mnt/disc

real    49m7.526s
user    0m26.278s
sys    12m37.627s

========================================

#include <stdio.h>
#include <fcntl.h>
#include <unistd.h>

#define __BYTES        8192
#define __FILES        1000

char    buf [__BYTES];

int main ()
{
    char    fname [1024];
    int        nFiles [__FILES];
    int     f, i;

    /* Fill buf */
    for (i = 0; i < __BYTES; i++)
        buf [i] = i % 128;

    /* Create and open files */
    for (f = 0; f < __FILES; f++) {
        sprintf (fname, "/mnt/disc/storage/file-%d", f);
        nFiles [f] = open (fname, O_WRONLY | O_CREAT | O_TRUNC, 0644);
    }

    for (i = 0; i < 262144; i++) {
        /* Write data to a big file */
        write (nFiles [0], buf, __BYTES);

        /* Write data to small files */
        for (f = 1; f < __FILES; f++)
            write (nFiles [f], &f, sizeof (f));
    }

    for (f = 0; f < __FILES; f++) {
        fsync (nFiles [f]);
        close (nFiles [f]);
    }

    return 0;
}

========================================

-- 
Igor A. Valcov

  reply	other threads:[~2006-11-10 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 17:30 Igor A. Valcov
2006-11-09 17:44 ` Eric Sandeen
2006-11-09 18:08 ` Russell Cattelan
2006-11-10  1:10   ` David Chinner
2006-11-10  3:36 ` Eric Sandeen
2006-11-10 11:59   ` Jan Engelhardt
2006-11-10 13:16     ` Igor A. Valcov [this message]
2006-11-10 14:44       ` Igor A. Valcov
2006-11-10 17:14       ` Eric Sandeen
2006-11-11  6:52       ` Andrew Morton
2006-11-11 10:55         ` Jan Engelhardt
2006-11-13 20:05 ` Tom Vier

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bde600590611100516u7b8ca1bfs74d3cc8b78eb3520@mail.gmail.com \
    --to=viaprog@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®