From: Wols Lists <antlists@youngman.org.uk>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Matt Garman <matthew.garman@gmail.com>
Cc: Mdadm <linux-raid@vger.kernel.org>
Subject: Re: kernel checksumming performance vs actual raid device performance
Date: Fri, 26 Aug 2016 19:11:47 +0100 [thread overview]
Message-ID: <57C08663.1000106@youngman.org.uk> (raw)
In-Reply-To: <83f67452-9f09-2d6f-f82a-77d83309f618@websitemanagers.com.au>
On 26/08/16 00:39, Adam Goryachev wrote:
> You should find out if you are swapping with vmstat:
> vmstat 5
> Watch the Swap (SI and SO) columns, if they are non-zero, then you are
> indeed swapping.
>
> You might find that if there is insufficient memory, then the kernel
> will automatically reduce/limit the value for the stripe_cache_size (I'm
> only guessing, but my memory tells me that the kernel locks this memory
> and it can't be swapped/etc).
Are you using a gui :-) ?
Download and build the latest version of xosview (assuming it builds,
when I last tried, "bleeding edge" was bleeding ... :-(
git://github.com/mromberg/xosview
That'll give you a nice little overview of both raid and swap. The
current version of xosview is fine for swap, but the raid monitor is broken.
Cheers,
Wol
prev parent reply other threads:[~2016-08-26 18:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:09 kernel checksumming performance vs actual raid device performance Matt Garman
2016-07-13 3:58 ` Brad Campbell
[not found] ` <CAFx4rwQj3_JTNiS0zsQjp_sPXWkrp0ggjg_UiR7oJ8u0X9PQVA@mail.gmail.com>
2016-07-13 16:52 ` Fwd: " Doug Dumitru
2016-08-16 19:44 ` Matt Garman
2016-08-16 22:51 ` Doug Dumitru
2016-08-17 0:27 ` Adam Goryachev
[not found] ` <CAFx4rwTawqrBOWVwtPnGhRRAM1XiGQkS-o3YykmD0AftR45YkA@mail.gmail.com>
2016-08-23 14:34 ` Matt Garman
2016-08-23 15:02 ` Chris Murphy
[not found] ` <CAJvUf-Dqesy2TJX7W-bPakzeDcOoNy0VoSWWM06rKMYMhyhY7g@mail.gmail.com>
[not found] ` <CAFx4rwSQQuqeCFm+60+Gm75D49tg+mVjU=BnQSZThdE7E6KqPQ@mail.gmail.com>
2016-08-23 14:54 ` Matt Garman
2016-08-23 18:00 ` Doug Ledford
2016-08-23 18:27 ` Doug Dumitru
2016-08-23 19:10 ` Doug Ledford
2016-08-23 19:19 ` Doug Dumitru
2016-08-23 19:26 ` Doug Ledford
2016-08-23 19:26 ` Matt Garman
2016-08-23 19:41 ` Doug Dumitru
2016-08-23 20:15 ` Doug Ledford
2016-08-23 21:42 ` Phil Turmel
2016-08-24 1:02 ` Shaohua Li
2016-08-25 15:07 ` Matt Garman
2016-08-25 23:39 ` Adam Goryachev
2016-08-26 13:01 ` Matt Garman
2016-08-26 20:04 ` Doug Dumitru
2016-08-26 21:57 ` Phil Turmel
2016-08-26 22:11 ` Doug Dumitru
2016-08-26 18:11 ` Wols Lists [this message]
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=57C08663.1000106@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=matthew.garman@gmail.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 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.