From: Viji V Nair <viji@fedoraproject.org>
To: reiserfs-devel@vger.kernel.org
Subject: reiserfs - recommendations for small files
Date: Sat, 17 Oct 2009 23:41:12 +0530 [thread overview]
Message-ID: <84c89ac10910171111n69b9832fr42d30aa07d84b262@mail.gmail.com> (raw)
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 are only writes, no
read. After generation there are heavy read and no write. 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
I am looking for an alternate file system and best
practices/recommendation to get a better performance. What the
optimisation methods available in reiserfs for small files?
Any suggestions of the above are greatly appreciated.
Viji
next reply other threads:[~2009-10-17 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 18:11 Viji V Nair [this message]
2009-10-19 19:16 ` reiserfs - recommendations for small files Toby Thain
2009-10-19 19:26 ` Viji V Nair
2009-10-19 23:34 ` Edward Shishkin
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=84c89ac10910171111n69b9832fr42d30aa07d84b262@mail.gmail.com \
--to=viji@fedoraproject.org \
--cc=reiserfs-devel@vger.kernel.org \
/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).