From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) by kanga.kvack.org (Postfix) with ESMTP id 670EB6B4C55 for ; Wed, 29 Aug 2018 11:14:13 -0400 (EDT) Received: by mail-wr1-f71.google.com with SMTP id y32-v6so3662422wrd.19 for ; Wed, 29 Aug 2018 08:14:13 -0700 (PDT) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id 132-v6sor1055271wmi.0.2018.08.29.08.14.12 for (Google Transport Security); Wed, 29 Aug 2018 08:14:12 -0700 (PDT) MIME-Version: 1.0 References: <20180821064911.GW29735@dhcp22.suse.cz> <11b4f8cd-6253-262f-4ae6-a14062c58039@suse.cz> <6ef03395-6baa-a6e5-0d5a-63d4721e6ec0@suse.cz> <20180823122111.GG29735@dhcp22.suse.cz> <76c6e92b-df49-d4b5-27f7-5f2013713727@suse.cz> <8b211f35-0722-cd94-1360-a2dd9fba351e@suse.cz> <20180829150136.GA10223@dhcp22.suse.cz> In-Reply-To: <20180829150136.GA10223@dhcp22.suse.cz> From: Marinko Catovic Date: Wed, 29 Aug 2018 17:13:59 +0200 Message-ID: Subject: Re: Caching/buffers become useless after some time Content-Type: multipart/alternative; boundary="0000000000002acb6c05749469b9" Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Vlastimil Babka , Christopher Lameter , linux-mm@kvack.org --0000000000002acb6c05749469b9 Content-Type: text/plain; charset="UTF-8" > > trace data which starts _before_ the cache dropdown starts and while it > is decreasing should be the first step. Ideally along with /proc/vmstat > gathered at the same time. I am pretty sure you have some high order > memory consumer which forces the reclaim and we over reclaim. Last data > was not really conclusive as it didn't really captured the dropdown > IIRC. > with before you mean in a totally healthy state? as I can not tell when decreasing starts this would mean collecting data over days perhaps. however, I have no issue with that. As I do not want to miss anything that might help you, could you please provide the commands for all the data you require? one host is at a healthy state right now, I'd run that over there immediately. --0000000000002acb6c05749469b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


trace data which starts _before_ the cache dropdown starts and while it
is decreasing should be the first step. Ideally along with /proc/vmstat
gathered at the same time. I am pretty sure you have some high order
memory consumer which forces the reclaim and we over reclaim. Last data
was not really conclusive as it didn't really captured the dropdown
IIRC.

with before you mean in a totally= healthy state?
as I can not tell when decreasing starts this wou= ld mean collecting data
over days perhaps. however, I have no iss= ue with that.
As I do not want to miss anything that might help y= ou, could you please
provide the commands for all the data you re= quire?
one host is at a healthy state right now, I'd run that= over there immediately.


--0000000000002acb6c05749469b9--