[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090406141516.GM3795@csclub.uwaterloo.ca>
Date: Mon, 6 Apr 2009 10:15:16 -0400
From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To: Jeff Moyer <jmoyer@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, tytso@....edu, drees76@...il.com,
jesper@...gh.cc, linux-kernel@...r.kernel.org,
jens.axboe@...cle.com
Subject: Re: Linux 2.6.29
On Fri, Apr 03, 2009 at 06:28:36PM -0400, Jeff Moyer wrote:
> Could you try one more test, please? Switch back to CFQ and set
> /sys/block/sdX/queue/iosched/slice_idle to 0?
I actually am running cfq at the moment, but with Mark's (I think it
was) preload library to change fsync calls to at most one per 5 seconds
instead of 10 per second. So far that has certainly made things a lot
better as far as I can tell. Maybe not as good as anticipatory seemed
to be but certainly better.
I can try your suggestion too.
I set sda-sdd to 0. I removed the preload library from the mythbackend.
> I'm not sure how the applications you are running write to disk, but if
> they interleave I/O between processes, this could help. I'm not too
> confident that this will make a difference, though, since CFQ changed to
> time-slice based instead of quantum based before 2.6.18. Still, it
> would be another data point if you have the time.
Well when recording two shows at once, there will be two processes
streaming to seperate files, and usually there will be two commercial
flagging processes following behind reading those files and doing mysql
updates as they go.
> Thanks in advance!
No problem. If it solves this bad behaviour, it will be all worth it.
--
Len Sorensen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists