From: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Non-blocking socket stuck for multiple seconds on xfs_reclaim_inodes_ag()
Date: Wed, 2 Jan 2019 11:34:09 +0100 [thread overview]
Message-ID: <2a57d498-bf0f-bf48-ff4f-89748660d28e@gmail.com> (raw)
In-Reply-To: <CABWYdi28ifToh-yWRAv4MSdJ9g6t-Rxyz2GAFXGFraCwf9BBDg@mail.gmail.com>
On 19/12/2018 23:15, Ivan Babrou wrote:
> We're sticking with the following patch that allows runtime switching
> between XFS memory reclaim strategies:
>
> * https://github.com/bobrik/linux/pull/2
>
> There are some tests and graphs describing the issue and how it can be solved.
>
> Let me know if you think this can be incorporated upstream, I'm fine if not.
This hack and fs.xfs.memory_reclaim=0 solved my problem where backup
server (doing rsnapshot, so tons of rsync+hardlinks+rm+cp of milions
files) was barely usable. Things like ssh or other network services were
stuck for 10-30 minutes doing reclaim.
Hack but for now server behaves much better than with vanilla kernel on
this type of workload.
Thanks,
(resend)
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
prev parent reply other threads:[~2019-01-02 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 0:36 Non-blocking socket stuck for multiple seconds on xfs_reclaim_inodes_ag() Ivan Babrou
2018-11-29 2:18 ` Dave Chinner
2018-11-29 14:36 ` Shawn Bohrer
2018-11-29 21:20 ` Dave Chinner
2018-11-29 22:22 ` Ivan Babrou
2018-11-30 2:18 ` Dave Chinner
2018-11-30 3:31 ` Ivan Babrou
2018-11-30 6:49 ` Dave Chinner
2018-11-30 7:45 ` Dave Chinner
2018-12-19 22:15 ` Ivan Babrou
2018-12-21 4:00 ` Kenton Varda
2018-12-25 23:47 ` Dave Chinner
2018-12-26 3:16 ` Kenton Varda
2018-12-29 19:05 ` Darrick J. Wong
2019-01-01 23:48 ` Dave Chinner
2019-01-02 10:34 ` Arkadiusz Miśkiewicz [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=2a57d498-bf0f-bf48-ff4f-89748660d28e@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=linux-xfs@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).