From: Benjamin LaHaise <bcrl@kvack.org>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Jan Kara <jack@suse.cz>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: add noorlov parameter to avoid spreading of directory inodes
Date: Wed, 2 Oct 2013 12:52:10 -0400 [thread overview]
Message-ID: <20131002165210.GA16076@kvack.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1310021838370.1924@localhost.localdomain>
On Wed, Oct 02, 2013 at 06:44:56PM +0200, Lukáš Czerner wrote:
> What is the frequency of unlink operation in comparison to file
> creation ? There is a possible issue with the global goal cursors
> s_mb_last_group and s_mb_last_start which might make your files
> increasingly scattered across the disk. I've attempted to address
> this problem with my patch
unlink() is 1:1 with creation. The storage on disk is essentially used
as an elastic buffer for the rest of the system. That said, unlink() may
not occur for minutes, hours or days.
In terms of actual allocation pattern on disk, using fallocate() is
sufficient to ensure that files on disk are usually limited to 1 extent,
and allocated immediately following each other. Without fallocate(), I
was seeing allocations aligned to 2048 block boundaries for 9MB files,
which hurt performance quite a bit.
> ext4: Try to better reuse recently freed space
>
> What is the usual size of the files this application is creating ?
It varies. The target is 8MB, but it ranges from 5MB to 22MB. In the
worst case it can be as small as 4KB.
-ben
> Thanks!
> -Lukas
--
"Thought is the essence of where you are now."
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-02 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 16:08 [PATCH] ext4: add noorlov parameter to avoid spreading of directory inodes Benjamin LaHaise
2013-10-02 14:47 ` Jan Kara
2013-10-02 15:02 ` Eric Sandeen
2013-10-02 15:25 ` Lukáš Czerner
2013-10-02 15:31 ` Benjamin LaHaise
2013-10-02 15:57 ` Jan Kara
2013-10-02 16:44 ` Lukáš Czerner
2013-10-02 16:52 ` Benjamin LaHaise [this message]
2013-10-02 17:09 ` Lukáš Czerner
2013-10-02 16:23 ` Theodore Ts'o
2013-10-02 17:02 ` Benjamin LaHaise
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=20131002165210.GA16076@kvack.org \
--to=bcrl@kvack.org \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).