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_at_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.Received on Sat Apr 18 2020 - 13:10:53 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:23 UTC