From: Timofey Titovets <timofey.titovets@synesis.ru>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH V3] KSM: allow dedup all tasks memory
Date: Tue, 13 Nov 2018 14:25:45 +0300 [thread overview]
Message-ID: <CAGqmi76_ftDGtyowNRz7CCxRoJ6U3L747M=dWbRjh357w3=ZKA@mail.gmail.com> (raw)
In-Reply-To: <20181113014928.GH21824@bombadil.infradead.org>
вт, 13 нояб. 2018 г. в 04:49, Matthew Wilcox <willy@infradead.org>:
>
> On Tue, Nov 13, 2018 at 02:13:44AM +0300, Timofey Titovets wrote:
> > Some numbers from different not madvised workloads.
> > Formulas:
> > Percentage ratio = (pages_sharing - pages_shared)/pages_unshared
> > Memory saved = (pages_sharing - pages_shared)*4/1024 MiB
> > Memory used = free -h
> >
> > * Name: My working laptop
> > Description: Many different chrome/electron apps + KDE
> > Ratio: 5%
> > Saved: ~100 MiB
> > Used: ~2000 MiB
>
> Your _laptop_ saves 100MB of RAM? That's extraordinary. Essentially
> that's like getting an extra 100MB of page cache for free. Is there
> any observable slowdown? I could even see there being a speedup (due
> to your working set being allowed to be 5% larger)
>
> I am now a big fan of this patch and shall try to give it the review
> that it deserves.
I'm not sure if this is sarcasm,
anyway i try do my best to get that working.
On any x86 desktop with mixed load (browser, docs, games & etc)
You will always see something like 40-200 MiB of deduped pages,
based on type of load of course.
I'm just don't try use that numbers as reason to get general KSM
deduplication in kernel.
Because in current generation with several gigabytes of memory,
several saved MiB not looks serious for most of people.
Thanks!
next prev parent reply other threads:[~2018-11-13 11:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 23:13 Timofey Titovets
2018-11-13 1:49 ` Matthew Wilcox
2018-11-13 11:25 ` Timofey Titovets [this message]
2018-11-13 2:25 ` Pavel Tatashin
2018-11-13 11:40 ` Timofey Titovets
2018-11-13 18:42 ` Pavel Tatashin
2018-11-13 22:55 ` Timofey Titovets
2018-11-13 11:57 ` Jann Horn
2018-11-13 12:58 ` Timofey Titovets
2018-11-13 13:25 ` Jann Horn
[not found] <<CAG48ez0ZprqUYGZFxcrY6U3Dnwt77q1NJXzzpsn1XNkRuXVppw@mail.gmail.com>
2018-11-13 14:23 ` Oleksandr Natalenko
2018-11-13 17:59 ` Pavel Tatashin
2018-11-13 18:17 ` Timofey Titovets
2018-11-13 18:35 ` Pavel Tatashin
2018-11-13 18:54 ` Timofey Titovets
2018-11-13 19:16 ` Pavel Tatashin
2018-11-13 22:40 ` Timofey Titovets
2018-11-13 22:53 ` Pavel Tatashin
2018-11-13 23:07 ` Timofey Titovets
2018-11-13 20:26 ` Jann Horn
2018-11-13 22:35 ` Pavel Tatashin
[not found] <<20181112231344.7161-1-timofey.titovets@synesis.ru>
2018-11-13 11:06 ` Oleksandr Natalenko
2018-11-13 11:56 ` Timofey Titovets
2018-11-13 16:33 ` Oleksandr Natalenko
2018-11-13 17:10 ` Timofey Titovets
2018-11-13 17:27 ` Oleksandr Natalenko
2018-11-13 17:44 ` Timofey Titovets
2018-11-13 18:20 Timofey Titovets
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='CAGqmi76_ftDGtyowNRz7CCxRoJ6U3L747M=dWbRjh357w3=ZKA@mail.gmail.com' \
--to=timofey.titovets@synesis.ru \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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