This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: About JSON output generated by "bench-malloc-thread"
- From: Francesco <francesco dot montorsi at gmail dot com>
- To: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- Cc: libc-help <libc-help at sourceware dot org>
- Date: Thu, 1 Feb 2018 13:38:47 +0100
- Subject: Re: About JSON output generated by "bench-malloc-thread"
- Authentication-results: sourceware.org; auth=none
- References: <CAKW0qigAOSW0CxkB==OuXBT4OZSkr_cggKcA0waZ+Sc6VG2pZA@mail.gmail.com> <CAAHN_R3WMJ_eMNZLoi6LZ+qqG9yrfdi=wjHUys_E+vjgWH7ocg@mail.gmail.com>
Hi Siddhesh,
thanks for fast answer.
I can also collaborate on that if you need.
Thanks,
Francesco
2018-02-01 13:08 GMT+01:00 Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
:
> On 1 February 2018 at 16:17, Francesco <francesco.montorsi@gmail.com>
> wrote:
> > Hi,
> > I was curious to run some benchmarks for different allocators and I found
> > out the benchtests/bench-malloc-thread utility.
> > However apparently it's producing a JSON output that is not following the
> > "benchout.schema.json" schema presnt under benchtests/scripts. Is this a
> > known/desired behavior?
> > (this is on latest git master branch)
> >
> > How am I supposed to graph the results of that benchmark utility?
> >
> > This is what I get calling "compare_bench.py":
>
> That schema is for the results in bench.out, which is for simpler
> functions and not for strings or malloc. I never wrote a script for
> malloc benchmarks since I never needed it. It might not be very hard
> to fix the script up for malloc, I'll take a look over the weekend and
> push a fix once 2.27 release is done.
>
> Siddhesh
>
>
>
> --
> http://siddhesh.in
>