[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKEwX=NMjfC1bKTVsB+C7eq3y=O0x3v8MW7KxUfhpg6UUr23rw@mail.gmail.com>
Date: Mon, 7 Apr 2025 08:51:12 -0700
From: Nhat Pham <nphamcs@...il.com>
To: Igor Belousov <igor.b@...dev.am>
Cc: vitaly.wool@...sulko.se, Johannes Weiner <hannes@...xchg.org>, linux-mm@...ck.org,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
Shakeel Butt <shakeel.butt@...ux.dev>
Subject: Re: [PATCH v2] mm: add zblock allocator
On Mon, Apr 7, 2025 at 2:00 AM Igor Belousov <igor.b@...dev.am> wrote:
>
>
> >>> Do you have zswap/zswapped meminfo metrics from these tests?
> >> Yep, and those look somewhat similar:
> >> - zblock:
> >> Zswap: 234128 kB
> >> Zswapped: 733216 kB
> >> - zsmalloc:
> >> Zswap: 286080 kB
> >> Zswapped: 774688 kB
> >
> > I tested the kernel build on a 4-core virtual machine with allocated 4
> > GB RAM running on a Ryzen 9.
> >
> > The results are the following:
> [...]
>
> Now what's funny is that when I tried to compare how 32 threaded build
> would behave on a 8-core VM I couldn't do it because it OOMs with
> zsmalloc as zswap backend. With zblock it doesn't, though, and the
> results are:
> real 12m14.012s
> user 39m37.777s
> sys 14m6.923s
> Zswap: 440148 kB
> Zswapped: 924452 kB
> zswpin 594812
> zswpout 2802454
> zswpwb 10878
>
> /Igor
May I ask what compression algorithm you are using?
And does the zswpwb come from zswap shrinker?
Powered by blists - more mailing lists