From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Julian Taylor <jtaylor.debian@googlemail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs and numa - needing drop_caches to keep speed up
Date: Fri, 14 Oct 2016 15:19:58 +0200 [thread overview]
Message-ID: <7b334ad0-0842-73ee-bc3e-adc6be41c839@profihost.ag> (raw)
In-Reply-To: <a358938d-aef4-f2c7-942b-6cee3d1d774e@googlemail.com>
Dear julian,
Am 14.10.2016 um 14:26 schrieb Julian Taylor:
> On 10/14/2016 08:28 AM, Stefan Priebe - Profihost AG wrote:
>> Hello list,
>>
>> while running the same workload on two machines (single xeon and a dual
>> xeon) both with 64GB RAM.
>>
>> I need to run echo 3 >/proc/sys/vm/drop_caches every 15-30 minutes to
>> keep the speed as good as on the non numa system. I'm not sure whether
>> this is related to numa.
>>
>> Is there any sysctl parameter to tune?
>>
>> Tested with vanilla v4.8.1
>>
>> Greets,
>> Stefan
>
> hi,
> why do you think this is related to btrfs?
was just an idea as i couldn't find any other difference between those
systems.
> This is easy to diagnose but recording some kernel stacks during the >
problem with perf.
you just mean perf top? Does it also show locking problems? As i see not
much CPU usage in that case.
> The only known issue that has this type of workaround that I know of are
> transparent huge pages.
I already disabled thp by:
echo never > /sys/kernel/mm/transparent_hugepage/enabled
cat /proc/meminfo says:
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Greets,
Stefan
>
> cheers,
> Julian
next prev parent reply other threads:[~2016-10-14 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 6:28 btrfs and numa - needing drop_caches to keep speed up Stefan Priebe - Profihost AG
2016-10-14 12:26 ` Julian Taylor
2016-10-14 13:19 ` Stefan Priebe - Profihost AG [this message]
2016-10-14 14:06 ` Stefan Priebe - Profihost AG
2016-10-14 12:48 ` 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=7b334ad0-0842-73ee-bc3e-adc6be41c839@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=jtaylor.debian@googlemail.com \
--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).