[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151022221054.GA2949757@devbig217.prn1.facebook.com>
Date: Thu, 22 Oct 2015 15:10:54 -0700
From: Dave Watson <davejwatson@...com>
To: Andy Lutomirski <luto@...capital.net>
CC: <kernel-team@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Paul Turner <pjt@...gle.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [RFC PATCH 0/3] restartable sequences benchmarks
On Thu, Oct 22, 2015 at 12:11:42PM -0700, Andy Lutomirski wrote:
> On Thu, Oct 22, 2015 at 11:06 AM, Dave Watson <davejwatson@...com> wrote:
> >
> > RSS CPUIDLE LATENCYMS
> > jemalloc 4.0.0 31G 33% 390
> > jemalloc + this patch 25G 33% 390
> > jemalloc + this patch using lsl 25G 30% 420
> > jemalloc + PT's rseq patch 25G 32% 405
> > glibc malloc 2.20 27G 30% 420
> > tcmalloc gperftools trunk (2.2) 21G 30% 480
>
> Slightly confused. This is showing a space efficiency improvement but
> not a performance improvement? Is the idea that percpu free lists are
> more space efficient than per-thread free lists?
>
> --Andy
Correct - the service was already tuned such that most requests hit
the (very large) thread free lists to avoided taking expensive locks
talking to the central arena. There were more threads than cpus, so
the memory win is just needing fewer free lists.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists