From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2191) id 5906C3858D37; Tue, 4 Aug 2020 23:53:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5906C3858D37 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Carlos O'Donell To: glibc-cvs@sourceware.org Subject: [glibc] benchtests/README update. X-Act-Checkin: glibc X-Git-Author: Paul Zimmermann X-Git-Refname: refs/heads/master X-Git-Oldrev: 45069ac2a994758d06c035804a600066016801f9 X-Git-Newrev: 50a8dd367e305bb6c6146c564fd48c193cc94069 Message-Id: <20200804235325.5906C3858D37@sourceware.org> Date: Tue, 4 Aug 2020 23:53:25 +0000 (GMT) X-BeenThere: glibc-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2020 23:53:25 -0000 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=50a8dd367e305bb6c6146c564fd48c193cc94069 commit 50a8dd367e305bb6c6146c564fd48c193cc94069 Author: Paul Zimmermann Date: Tue Aug 4 13:27:39 2020 +0200 benchtests/README update. Improve documentation of the 'name' directive and the 'workload' mechanism. Reviewed-by: Carlos O'Donell Diff: --- benchtests/README | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/benchtests/README b/benchtests/README index f440f3295a..44736d7e63 100644 --- a/benchtests/README +++ b/benchtests/README @@ -125,17 +125,25 @@ math functions perform computations at different levels of precision (64-bit vs performance of these functions. One could separate inputs for these domains in the same file by using the `name' directive that looks something like this: - ##name: 240bit + ##name: 240bits -See the pow-inputs file for an example of what such a partitioned input file -would look like. +All inputs after the ##name: 240bits directive and until the next `name' +directive (or the end of file) are part of the "240bits" benchmark and +will be output separately in benchtests/bench.out. See the pow-inputs file +for an example of what such a partitioned input file would look like. -It is also possible to measure throughput of a (partial) trace extracted from -a real workload. In this case the whole trace is iterated over multiple times -rather than repeating every input multiple times. This can be done via: +It is also possible to measure latency and reciprocal throughput of a +(partial) trace extracted from a real workload. In this case the whole trace +is iterated over multiple times rather than repeating every input multiple +times. This can be done via: ##name: workload- +where is simply used to distinguish between different traces in the +same file. To create such a trace, you can simply extract using printf() +values uses for a specific application, or generate random values in some +interval. See the expf-inputs file for an example of this workload mechanism. + Benchmark Sets: ==============