From: Viji V Nair <viji@fedoraproject.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext3-users@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: optimising filesystem for many small files
Date: Sat, 17 Oct 2009 23:26:04 +0530 [thread overview]
Message-ID: <84c89ac10910171056i773dfb93wc2e917a086dd8ef0@mail.gmail.com> (raw)
In-Reply-To: <4AD9D599.3000306@redhat.com>
these files are not in a single directory, this is a pyramid
structure. There are total 15 pyramids and coming down from top to
bottom the sub directories and files are multiplied by a factor of 4.
The IO is scattered all over!!!! and this is a single disk file system.
Since the python application is creating files, it is creating
multiple files to multiple sub directories at a time.
On Sat, Oct 17, 2009 at 8:02 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> Viji V Nair wrote:
>>
>> Hi,
>>
>> System : Fedora 11 x86_64
>> Current Filesystem: 150G ext4 (formatted with "-T small" option)
>> Number of files: 50 Million, 1 to 30K png images
>>
>> We are generating these files using a python programme and getting very
>> slow IO performance. While generation there in only write, no read. After
>> generation there is heavy read and no write.
>>
>> I am looking for best practices/recommendation to get a better
>> performance.
>>
>> Any suggestions of the above are greatly appreciated.
>>
>> Viji
>>
>
> I would start with using blktrace and/or seekwatcher to see what your IO
> patterns look like when you're populating the disk; I would guess that
> you're seeing IO scattered all over.
>
> How you are placing the files in subdirectories will affect this quite a
> lot; sitting in 1 directory for a while, filling with images, before moving
> on to the next directory, will probably help. Putting each new file in a
> new subdirectory will probably give very bad results.
>
> -Eric
>
--
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:[~2009-10-17 17:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 6:52 optimising filesystem for many small files Viji V Nair
2009-10-17 14:32 ` Eric Sandeen
2009-10-17 17:56 ` Viji V Nair [this message]
2009-10-17 22:26 ` Theodore Tso
2009-10-18 9:31 ` Viji V Nair
2009-10-18 11:25 ` Jon Burgess
2009-10-18 12:51 ` Viji V Nair
2009-10-18 11:41 ` Matija Nalis
2009-10-18 13:08 ` Fwd: " Viji V Nair
2009-10-19 7:23 ` Stephen Samuel (gmail)
2009-10-18 13:14 ` Viji V Nair
2009-10-18 15:07 ` Jon Burgess
2009-10-18 16:29 ` Viji V Nair
2009-10-18 17:15 ` Jon Burgess
2009-10-18 14:15 ` Peter Grandi
2009-10-18 16:10 ` Viji V Nair
2009-10-18 15:34 ` Eric Sandeen
2009-10-18 16:33 ` Viji V Nair
-- strict thread matches above, loose matches on Subject: below --
2009-10-17 6:59 Viji V Nair
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=84c89ac10910171056i773dfb93wc2e917a086dd8ef0@mail.gmail.com \
--to=viji@fedoraproject.org \
--cc=ext3-users@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).