From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: More memory more jitters?
Date: Sat, 14 Nov 2015 16:37:14 +0000 (UTC) [thread overview]
Message-ID: <pan$ce09f$d4f4e93$fd67914e$33e263e1@cox.net> (raw)
In-Reply-To: 20151114143112.GK24333@carfax.org.uk
Hugo Mills posted on Sat, 14 Nov 2015 14:31:12 +0000 as excerpted:
>> I have read the Gotcha[1] page:
>>
>> Files with a lot of random writes can become heavily fragmented
>> (10000+ extents) causing trashing on HDDs and excessive multi-second
>> spikes of CPU load on systems with an SSD or **large amount a RAM**.
>>
>> Why could large amount of memory worsen the problem?
>
> Because the kernel will hang on to lots of changes in RAM for
> longer. With less memory, there's more pressure to write out dirty pages
> to disk, so the changes get written out in smaller pieces more often.
> With more memory, the changes being written out get "lumpier".
>
>> If **too much** memory is a problem, is it possible to limit the memory
>> btrfs use?
>
> There's some VM knobs you can twiddle, I believe, but I haven't
> really played with them myself -- I'm sure there's more knowledgable
> people around here who can suggest suitable things to play with.
Yes. Don't have time to explain now, but I will later, if nobody beats
me to it.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-11-14 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 14:11 More memory more jitters? CHENG Yuk-Pong, Daniel
2015-11-14 14:31 ` Hugo Mills
2015-11-14 16:37 ` Duncan [this message]
2015-11-15 7:40 ` Duncan
2015-11-15 16:58 ` Patrik Lundquist
2015-11-16 13:34 ` Austin S Hemmelgarn
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='pan$ce09f$d4f4e93$fd67914e$33e263e1@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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