From: Mike Fleetwood <mike.fleetwood@googlemail.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: commands like "du", "df", and "btrfs fs sync" hang
Date: Sun, 1 May 2016 14:54:44 +0100 [thread overview]
Message-ID: <CAMU1PDj99OSwFy7Ep9g43uezNLEGoziqPn3kzhUUqeEMRNTWgg@mail.gmail.com> (raw)
In-Reply-To: <pan$1c3f$713ccc59$ba5354e3$ceefdfd6@cox.net>
On 1 May 2016 at 13:47, Duncan <1i5t5.duncan@cox.net> wrote:
> Direct from that section of my /etc/sysctl.conf:
>
> ################################################################################
> # Virtual-machine: swap, write-cache
Hi Duncan,
You mean virtual memory.
Quoting from the kernel documentation
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/sysctl/vm.txt
"
This file contains the documentation for the sysctl files in
/proc/sys/vm and is valid for Linux kernel version 2.6.29.
The files in this directory can be used to tune the operation
of the virtual memory (VM) subsystem of the Linux kernel and
the writeout of dirty data to disk.
"
> # vm.vfs_cache_pressure = 100
> # vm.laptop_mode = 0
> # vm.swappiness = 60
> vm.swappiness = 100
>
> # write-cache, foreground/background flushing
> # vm.dirty_ratio = 10 (% of RAM)
> # make it 3% of 16G ~ half a gig
> vm.dirty_ratio = 3
> # vm.dirty_bytes = 0
>
> # vm.dirty_background_ratio = 5 (% of RAM)
> # make it 1% of 16G ~ 160 M
> vm.dirty_background_ratio = 1
> # vm.dirty_background_bytes = 0
>
> # vm.dirty_expire_centisecs = 2999 (30 sec)
> # vm.dirty_writeback_centisecs = 499 (5 sec)
> # make it 10 sec
> vm.dirty_writeback_centisecs = 1000
> ################################################################################
Thanks,
Mike
next prev parent reply other threads:[~2016-05-01 13:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 7:00 commands like "du", "df", and "btrfs fs sync" hang Kai Krakow
2016-05-01 12:47 ` Duncan
2016-05-01 13:54 ` Mike Fleetwood [this message]
2016-05-01 23:16 ` Duncan
2016-05-01 16:54 ` Kai Krakow
2016-05-01 23:22 ` Duncan
2016-05-01 23:49 ` Duncan
2016-05-02 13:19 ` Austin S. Hemmelgarn
2016-05-03 6:44 ` Kai Krakow
2016-05-02 0:23 ` Duncan
2016-05-02 13:13 ` Austin S. Hemmelgarn
2016-05-03 15:09 ` Duncan
2016-05-02 0:39 ` Nicholas D Steeves
2016-05-03 6:48 ` Kai Krakow
2016-05-05 6:35 ` Kai Krakow
2016-05-07 11:40 ` Kai Krakow
2016-05-09 17:13 ` Nicholas D Steeves
2016-05-09 18:20 ` Kai Krakow
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 10:22 Kai Krakow
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=CAMU1PDj99OSwFy7Ep9g43uezNLEGoziqPn3kzhUUqeEMRNTWgg@mail.gmail.com \
--to=mike.fleetwood@googlemail.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).