From: "jehan.procaccia" <jehan.procaccia@int-evry.fr>
Cc: "Lever, Charles" <Charles.Lever@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: async vs. sync
Date: Wed, 24 Nov 2004 19:45:25 +0100 [thread overview]
Message-ID: <41A4D6C5.2060902@int-evry.fr> (raw)
In-Reply-To: <41A3AFC4.6080404@int-evry.fr>
Good advice :-), externalizing the journal from my FS on the AX100 SP to
an internal SCSI disk on the NFS server is very good in terms of
performances, now it take 1,5 minutes instead of 12m to unter httpd
archive !
Journal on a 16 Mo partition , export sync, mount async
[root@arvouin /mnt/cobra3extjournaldata16/Nfs-test16]
$time tar xvfz /usr/src/redhat/SOURCES/httpd-2.0.51.tar.gz
real 1m35.097s
user 0m0.872s
sys 0m2.409s
However now the tar extraction goes very fast but stops 1 or 2 or and
restart fast -> there are some hangs. Here with a 16MB journal I got 15
hangs of 1-2 seconds, with a 128 MB I get only 3 hangs but they last 4or
5 seconds. I checked at a momment of an hang on the nfs server with
iostat, and disk utilisation goes from a few % to 316 % in the exemple
below (for 128 MB journal withing the 4 seconds hangs it goes to 4700 % !)
Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s rkB/s wkB/s
avgrq-sz avgqu-sz await svctm %util
/dev/emcpowerl2
0.00 150.67 97.33 224.00 768.00 3018.67 384.00
1509.33 11.78 33.33 19.79 9.83 316.00
Maybe it hangs because the journal commits on the SP ! ?
Well, finally, is this safer in terms of performances to externalize
journal than using async export ?
And is it possible to externalize a journal on an already existing ext3
FS or do we need to reformat it ?
Thanks.
jehan procaccia wrote:
> Lever, Charles wrote:
>
>>
>> btw, it is fairly well understood that RAID-5 and NFS servers don't mix
>> well. RAID-5's weakest point is that it doesn't handle small random
>> writes very well, and that's exactly what is required of it when
>> handling NFS traffic that consists mostly of metadata changes (file
>> creates, deletes, and so on). neil explained clearly how to make the
>> best use of a RAID-5 with NFS: do your local file system journaling
>> somewhere else.
>>
>>
> No, not yet, but if it is safer and increase performances maybe I
> should do it !
>
> Perhaps it's not the place to talk about ext3 here, but if someone on
> the list did already put their journal on a separate device, please
> confirm me those points:
> From what I read on man mkefs for ext3 FS I can create a journal on a
> separate FS :
> mke2fs -O journal_dev external-journal
> creates the journal FS, on which device ? -> internal scsi drive of my
> server or better placed on the dell/EMC SP ?
>
> mke2fs -J device=/dev/external-journal /dev/emcpower
> Format the FS and use the external journal just create above, but what
> is the recommended size of the external journal ? when journal is
> internal it is said the size of the journal must be at least 1024
> filesystem blocks
> (in my case blocks a 4K size) so journal is at least 4 Mb, but should
> it be bigger ?
>
> Finally, can I "externalize" an already internal journal from
> production FS (convert journal from inside to outside without
> reformating the FS ) ?
>
> thanks.
>
>
>> when trying your workload locally on the NFS server, realize that there
>> are some optimizations that local file systems make, like caching and
>> coalescing metadata updates, that the NFS protocol does not allow. this
>> affects especially workloads with lots of metadata change operations,
>> because the NFS protocol requires each metadata update to reside on
>> permanent storage before the NFS server replies to the client,
>> effectively serializing the workload with storage activity.
>>
>>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-11-24 18:45 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 14:30 async vs. sync Lever, Charles
2004-11-23 21:46 ` jehan procaccia
2004-11-24 18:45 ` jehan.procaccia [this message]
2004-11-24 22:24 ` Neil Brown
2004-11-24 23:14 ` jehan procaccia
2004-11-24 23:34 ` Neil Brown
2004-11-24 22:09 ` Neil Brown
[not found] ` <Pine.GSO.4.53.0412010900500.5486@int1.cdc.noaa.gov>
2004-12-01 17:27 ` jehan.procaccia
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 19:05 Lever, Charles
2004-11-23 16:36 Lever, Charles
2004-11-23 18:16 ` Dan Stromberg
2004-11-23 3:53 Lever, Charles
2004-11-23 16:33 ` Dan Stromberg
2004-11-22 22:14 Lever, Charles
[not found] <20041122214605.8E2B31D0FE1@sc8-sf-uberspam1.sourceforge.net>
2004-11-22 21:57 ` Joshua Baker-LePain
2004-11-22 21:50 Lever, Charles
2004-11-22 22:06 ` jehan procaccia
2004-11-23 1:09 ` Dan Stromberg
2004-11-22 19:02 Lever, Charles
2004-11-22 21:25 ` jehan procaccia
2004-11-22 21:45 ` Nicolas.Kowalski
2004-11-22 23:51 ` jehan procaccia
2004-11-22 18:31 Lever, Charles
2004-11-16 18:48 Lever, Charles
2004-11-22 15:36 ` Olaf Kirch
2004-11-22 17:55 ` jehan.procaccia
2004-11-22 18:06 ` Roger Heflin
2004-11-22 18:46 ` jehan.procaccia
2004-11-22 19:10 ` Roger Heflin
2004-11-22 21:44 ` jehan procaccia
2004-11-22 21:52 ` jehan procaccia
2004-11-22 22:20 ` Trond Myklebust
2004-11-22 22:57 ` jehan procaccia
2004-11-23 9:50 ` jehan procaccia
2004-11-23 14:57 ` J. Bruce Fields
2004-11-22 18:08 ` Trond Myklebust
2004-11-22 18:57 ` jehan.procaccia
2004-11-22 19:05 ` Roger Heflin
2004-11-22 20:14 ` Trond Myklebust
2004-11-22 21:04 ` Paul Cunningham
2004-11-22 21:14 ` Trond Myklebust
2004-11-22 22:07 ` Paul Cunningham
2004-11-22 22:26 ` Trond Myklebust
2004-11-16 18:45 Lever, Charles
2004-11-16 16:15 Lever, Charles
2004-11-16 16:32 ` Trond Myklebust
2004-11-16 17:18 ` jehan.procaccia
2004-11-16 18:08 ` Trond Myklebust
[not found] <482A3FA0050D21419C269D13989C61130435E530@lavender-fe.eng.netapp.com>
2004-07-27 15:07 ` Bernd Schubert
2004-07-26 23:05 John Roberts
[not found] <482A3FA0050D21419C269D13989C61130435E523@lavender-fe.eng.netapp.com>
2004-07-26 21:28 ` Bernd Schubert
[not found] <482A3FA0050D21419C269D13989C61130435E51E@lavender-fe.eng.netapp.com>
2004-07-26 17:05 ` Bernd Schubert
2004-07-26 19:47 ` Jan Bruvoll
2004-07-26 22:06 ` Bernd Schubert
2004-07-27 12:00 ` Jan Bruvoll
2004-07-27 13:00 ` Bernd Schubert
2004-07-27 13:56 ` raven
2004-07-27 14:04 ` Jan Bruvoll
2004-07-27 14:11 ` Jan Bruvoll
2004-07-28 8:56 ` Olaf Kirch
2004-07-28 12:35 ` Bernd Schubert
2004-07-28 12:49 ` Olaf Kirch
2004-07-23 16:20 Linux NFS writes to Solaris very, very slow John Roberts
2004-07-26 15:17 ` async vs. sync Bernd Schubert
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=41A4D6C5.2060902@int-evry.fr \
--to=jehan.procaccia@int-evry.fr \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.