This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
time unit in bench-skeleton
- From: Victor Rodriguez <vm dot rod25 at gmail dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 27 Jun 2017 16:59:06 -0700
- Subject: time unit in bench-skeleton
- Authentication-results: sourceware.org; auth=none
Hi
I am trying to port the bench test to a most stable and usable
platform like https://openbenchmarking.org/ in order to give others
the capability to measure the performance of new glibc releases
I am trying to understand the output of bench.out:
"ffsll": {
"": {
"duration": 2.3834e+10,
"iterations": 5.5869e+09,
"max": 54.589,
"min": 4.246,
"mean": 4.26605
}
duration according to benchtests/bench-timing.h
42 /* Measure the resolution of the clock so we can scale the number of
43 benchmark iterations by this value. */
44 # define TIMING_INIT(res) \
45 ({ \
46 struct timespec start; \
47 clock_getres (CLOCK_PROCESS_CPUTIME_ID, &start); \
48 (res) = start.tv_nsec; \
49 })
is in nanoseconds right?
I am planign to parse the present the mean value , acording to:
118 json_attr_double (&json_ctx, "duration", d_total_s);
119 json_attr_double (&json_ctx, "iterations", d_total_i);
120 json_attr_double (&json_ctx, "max", max / d_iters);
121 json_attr_double (&json_ctx, "min", min / d_iters);
122 json_attr_double (&json_ctx, "mean", d_total_s / d_total_i);
seems to me the fairest comparison
Any feedback is more than welcome
Regards
Victor Rodriguez