Date: Sat, 18 Apr 2020 18:10:50 +0300 From: Yuri Pankov <ypankov@fastmail.com> To: Gordon Bergling <gbergling@googlemail.com>, Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: Outdated jemalloc in CURRENT Message-ID: <1f4e0642-8dff-612c-526a-2bfcbc0e5085@fastmail.com> In-Reply-To: <20200418150108.GA14089@lion.0xfce3.net> References: <1587211096.573263000.1z45j66i@frv55.fwdcdn.com> <20200418142003.GA64067@troutmask.apl.washington.edu> <20200418150108.GA14089@lion.0xfce3.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Gordon Bergling wrote: > I am not sure, that this info is correct. As far as I remember the update for jemalloc was reverted due to build problems, on some architecture. An updated revision has still to be commited to -CURRENT. That's exactly what the commit log says, yes? > On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote: >> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonameless@ukr.net wrote: >>> Hi everyone! >>> >>> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some performance regressions that was fixed in 5.2.1. >>> >>> Are there some issues that blocking update jemalloc to recent version? >>> >> >> ------------------------------------------------------------------------ >> r354606 | jasone | 2019-11-10 21:06:49 -0800 (Sun, 10 Nov 2019) | 4 lines >> >> Revert r354605: Update jemalloc to version 5.2.1. >> >> Compilation fails for non-llvm-based platforms. >> >> ------------------------------------------------------------------------ >> r354605 | jasone | 2019-11-10 19:27:14 -0800 (Sun, 10 Nov 2019) | 2 lines >> >> Update jemalloc to version 5.2.1.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f4e0642-8dff-612c-526a-2bfcbc0e5085>