From: Ivan Babrou <ivan@cloudflare.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: cgroups@vger.kernel.org, Linux MM <linux-mm@kvack.org>,
kernel-team <kernel-team@cloudflare.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Expensive memory.stat + cpu.stat reads
Date: Fri, 14 Jul 2023 17:14:19 -0700 [thread overview]
Message-ID: <CABWYdi2L_qp8SmZ_w3pSSracYHEVku3TaBoXL7E0Nzn7CN3neg@mail.gmail.com> (raw)
In-Reply-To: <CABWYdi2pBaCrdKcM37oBomc+5W8MdRp1HwPpOExBGYfZitxyWA@mail.gmail.com>
On Mon, Jul 10, 2023 at 4:21 PM Ivan Babrou <ivan@cloudflare.com> wrote:
> The fast one is v6.1.37 and the slow one is v6.1.25. I'm not sure if
> the kernel version makes a difference or if it's a matter of uptime /
> traffic profile. The data is from two different locations. The fast
> location has gone through an expansion, which meant a full reboot with
> a kernel upgrade, so maybe that affected things:
>
> * https://i.imgur.com/x8uyMaF.png
>
> Let me try to reboot the slow location and see if there's any lasting
> improvement.
There is no correlation with the kernel version, v6.1.38 is slow too:
completed: 23.09s [manual / cpu-stat + mem-stat]
completed: 0.30s [manual / mem-stat]
completed: 0.64s [manual / cpu-stat]
next prev parent reply other threads:[~2023-07-15 0:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 23:22 Ivan Babrou
2023-07-06 6:20 ` Shakeel Butt
2023-07-10 23:21 ` Ivan Babrou
2023-07-11 0:44 ` Waiman Long
2023-07-13 23:25 ` Ivan Babrou
2023-07-14 17:23 ` Waiman Long
2023-07-15 0:00 ` Ivan Babrou
2023-07-15 0:30 ` Ivan Babrou
2023-08-11 22:03 ` Ivan Babrou
2023-08-11 22:27 ` Waiman Long
2023-08-11 22:35 ` Ivan Babrou
2023-08-12 2:33 ` Shakeel Butt
2023-08-14 17:56 ` Ivan Babrou
2023-08-11 23:43 ` Yosry Ahmed
2023-08-12 0:01 ` Yosry Ahmed
2023-08-15 0:18 ` Tejun Heo
2023-08-15 0:30 ` Ivan Babrou
2023-08-15 0:31 ` Yosry Ahmed
2023-07-15 0:14 ` Ivan Babrou [this message]
2023-07-10 14:44 ` Michal Koutný
2023-07-10 23:23 ` Ivan Babrou
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=CABWYdi2L_qp8SmZ_w3pSSracYHEVku3TaBoXL7E0Nzn7CN3neg@mail.gmail.com \
--to=ivan@cloudflare.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox