From: Emmanuel Florac <eflorac@intellique.com>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs write performance issue
Date: Thu, 19 Mar 2015 18:10:56 +0100 [thread overview]
Message-ID: <20150319181056.6bbb013d@harpe.intellique.com> (raw)
In-Reply-To: <8976870.8vOdNBKrI1@xrated>
Le Thu, 19 Mar 2015 18:01:50 +0100
Hans-Peter Jansen <hpj@urpla.net> écrivait:
> Write performance is disastrous: it's about 1.5 MB/s.
>
write cache is probably off. RAID array performance with write cache
off usually falls to abysmal levels. Check that your RAID controller
has write cacne enabled.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-03-19 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:01 xfs write performance issue Hans-Peter Jansen
2015-03-19 17:10 ` Emmanuel Florac [this message]
2015-03-19 23:18 ` Dave Chinner
2015-03-20 8:05 ` Hans-Peter Jansen
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=20150319181056.6bbb013d@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=hpj@urpla.net \
--cc=xfs@oss.sgi.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