This is the mail archive of the
mailing list for the glibc project.
Re: Summary for the glibc benchmark BoF
- From: Siddhesh Poyarekar <siddhesh at redhat dot com>
- To: Steven Munroe <munroesj at linux dot vnet dot ibm dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 19 Aug 2015 10:34:16 +0530
- Subject: Re: Summary for the glibc benchmark BoF
- Authentication-results: sourceware.org; auth=none
- References: <20150818080953 dot GG2415 at spoyarek dot pnq dot redhat dot com> <1439925005 dot 569 dot 13 dot camel at oc7878010663>
On Tue, Aug 18, 2015 at 02:10:05PM -0500, Steven Munroe wrote:
> I don't think IBM is saying that the current benchmarks are complete or
> completely representative. We are saying that current benchmarks are
> what we have, and a assertion that the lack of some hypothetical
> "better" benchmark, should not be used as an excuse to block a patch.
OK, thanks for clarifying that. FWIW, I did not mean to imply that
you thought that the benchmarks were complete. I meant to say that
you think they're not useless or misleading enough that they should be
ripped out altogether.
> I would personally like to see more representative benchmarks based on
> actual usage.
+1. I've made calls in the past to enhance the inputs or even rewrite
the string benchmarks. The current benchmarks only measure raw
performance for very specific types of input (i.e. aligned at certain
boundaries, misaligned, etc.) and don't even try to pretend to
represent any kind of generic workload. If there are workloads that
matter, contributors should enhance the benchmark to provide that as
My hope is that full system benchmark workloads would give us that,
but that's as concrete right now as any other claim of representative
> I would also assert that benchmarks should be split into representative
> (of normal usage) and extreme (for example testing for quadratic
> behavior or only testing for the needle match at the very end of the
> haystack) categories. And clearly labeled as such.