> On Sat, Apr 18, 2020 at 11:22 PM Steve
> Kargl
> wrote:
> >
> > On Sat, Apr 18, 2020 at 05:01:08PM
> > +0200, Gordon Bergling wrote:
> > >
> > > On Sat, Apr 18, 2020 at 07:20:03AM
> > > -0700, Steve Kargl wrote:
> > >> On Sat, Apr 18, 2020 at 03:05:25PM
> > >> +0300, nonamel...@ukr.net wrote
On Sat, Apr 18, 2020 at 11:22 PM Steve Kargl
wrote:
>
> On Sat, Apr 18, 2020 at 05:01:08PM +0200, Gordon Bergling wrote:
> >
> > On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote:
> >> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@ukr.net wrote:
> >>> Hi everyone!
> >>>
> >>> As I
On Sat, Apr 18, 2020 at 05:01:08PM +0200, Gordon Bergling wrote:
>
> On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote:
>> On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@ukr.net wrote:
>>> Hi everyone!
>>>
>>> As I see, CURRENT still uses outdated jemalloc 5.1.0 with some
>>> perf
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.
Gordon
On Sat, Apr 18, 2020 at 07:20:03AM -0700, Steve Kargl wrote:
> On Sat, Apr 18, 2020 a
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, 202
On Sat, Apr 18, 2020 at 03:05:25PM +0300, nonamel...@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?
>
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?
Thanks.
___
freebsd-current@freebsd.org mailing list
ht
