From: "Stephen Samuel (gmail)" <darkonc@gmail.com>
To: Viji V Nair <viji@fedoraproject.org>
Cc: Matija Nalis <mnalis-ml@voyager.hr>,
linux-ext4@vger.kernel.org, ext3-users@redhat.com
Subject: Re: optimising filesystem for many small files
Date: Mon, 19 Oct 2009 00:23:30 -0700 [thread overview]
Message-ID: <6cd50f9f0910190023i5d719543n21862725c294aef3@mail.gmail.com> (raw)
In-Reply-To: <84c89ac10910180608v76caf7f5y4837ccaf6a66a594@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2119 bytes --]
On Sun, Oct 18, 2009 at 6:08 AM, Viji V Nair <viji@fedoraproject.org> wrote:
> From: Matija Nalis <mnalis-ml@voyager.hr>
>
> On Sun, Oct 18, 2009 at 03:01:46PM +0530, Viji V Nair wrote:
> > The application which we are using are modified versions of mapnik and
> > tilecache, these are single threaded so we are running 4 process at a
>
> How does it scale if you reduce the number or processes - especially if you
> run just one of those ? As this is just a single disk, 4 simultaneous
> readers/writers would probably *totally* kill it with seeks.
>
> I suspect it might even run faster with just 1 process then with 4 of
> them...
>
> with one process it is giving me 6 seconds
>
If it takes 6 seconds with one process and 20 seconds with 4 processes, then
this
pretty clearly points to problems with thrashing the heads.
(this presumes that the timing you're mentioning is time between request
and
service with the same request patterns).
Others have suggested flash drives... This sounds like an idea. On the
cheaper end, I'd suggest lots of mirroring.. The more drives the merrier. a
4-way mirrir will probably give you a good deal of speedup. If you can
find an old RAID box, try throwing in a dozen or so smaller drives (even 72
or 36GB SCSI drives)..
It sounds like the problem is clearly head seek, not transfer speeds, so
lots of old SCSI drives with a single (slower) connection will probably do
you more good than 4 demon-fast SATA drives.
If you have smaller drives, go to raid10. If you have larger drives, then go
to raid 1 and mirror them up the wazoo. (I'm presuming that this is a
read-mostly application. If you're doing lots of parallel writes, then raid
10 might still be a good idea, even with big drives).
If you already have a deep mirror and you later get Flash drives, then I'd
say add the flash drives into the mix, rather than just replacing the RAID
with flash, again -- unless this isn't a read-mostly situation -- the more
drives the merrier.
Stephen Samuel http://www.bcgreen.com Software, like love,
778-861-7641 grows when you give it away
[-- Attachment #1.2: Type: text/html, Size: 2654 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
next prev parent reply other threads:[~2009-10-19 7:23 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
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) [this message]
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=6cd50f9f0910190023i5d719543n21862725c294aef3@mail.gmail.com \
--to=darkonc@gmail.com \
--cc=ext3-users@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mnalis-ml@voyager.hr \
--cc=viji@fedoraproject.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).