public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Wesley <awesley@acquerra.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: nate.diller@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.13 buffer strangeness - ext2/3/reiser4/xfs comparison
Date: Sat, 10 Sep 2005 21:56:15 +1000	[thread overview]
Message-ID: <4322C9DF.1090704@acquerra.com.au> (raw)
In-Reply-To: <20050910044240.4e8e8e03.akpm@osdl.org>

Andrew Morton wrote:

> Anthony Wesley <awesley@acquerra.com.au> wrote:
> 
>>I compared ext2,ext3,xfs,vfat,reiser and reiser4.
>>
>> The hands-down winner was ext2. All the others showed problems of either lower disk throughput
>> or dropped frames during video capture.
> 
> 
> ext2 is a good filesystem.  For that sort of application all the journaling
> gunk can really get in the way.
> 
> You should have tested ext3 with data=writeback.
> 

Ask and ye shall receive...

I created an ext3 fs, mounted it with data=writeback and gave it a quick spin.

The result? Lots of pauses and dropped frames during capture. This is during the part of the
process where I have gobs of free RAM that's being used for buffering so dropping frames here
is a cardinal sin.

Dunno why it's happening, but I saw it also with xfs and reiser4. ext2 on the other hand
chugs along happily, no pauses, no dropped frames until we run out of free RAM (takes about 2
minutes now after the simple kernel change).

I can understand dropped frames after we run out of ram, but not before.

regards, Anthony

-- 
Anthony Wesley
Director and IT/Network Consultant
Smart Networks Pty Ltd
Acquerra Pty Ltd

Anthony.Wesley@acquerra.com.au
Phone: (02) 62595404 or 0419409836

  reply	other threads:[~2005-09-10 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09  9:11 kernel 2.6.13 buffer strangeness Anthony Wesley
2005-09-09 15:09 ` Roger Heflin
2005-09-09 21:39   ` Nate Diller
2005-09-10  0:16     ` Anthony Wesley
2005-09-10  0:35       ` Nate Diller
2005-09-10  1:07         ` Anthony Wesley
2005-09-10  1:47           ` Nate Diller
2005-09-10  2:23             ` Anthony Wesley
     [not found]               ` <5c49b0ed05090922021b8f8112@mail.gmail.com>
2005-09-10  5:32                 ` Anthony Wesley
2005-09-10  6:02                 ` kernel 2.6.13 buffer strangeness - FIXED Anthony Wesley
2005-09-10 10:23                 ` kernel 2.6.13 buffer strangeness - ext2/3/reiser4/xfs comparison Anthony Wesley
2005-09-10 11:42                   ` Andrew Morton
2005-09-10 11:56                     ` Anthony Wesley [this message]
2005-09-10  0:50     ` kernel 2.6.13 buffer strangeness Anthony Wesley
2005-09-10  5:41       ` Andrew Morton

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=4322C9DF.1090704@acquerra.com.au \
    --to=awesley@acquerra.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nate.diller@gmail.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