You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2019/01/21 17:15:00 UTC

[jira] [Created] (ARROW-4313) Define general benchmark database schema

Wes McKinney created ARROW-4313:
-----------------------------------

             Summary: Define general benchmark database schema
                 Key: ARROW-4313
                 URL: https://issues.apache.org/jira/browse/ARROW-4313
             Project: Apache Arrow
          Issue Type: New Feature
          Components: Benchmarking
            Reporter: Wes McKinney
             Fix For: 0.13.0


Some possible attributes that the benchmark database should track, to permit heterogeneity of hardware and programming languages

* Timestamp of benchmark run
* Git commit hash of codebase
* Machine unique name (sort of the "user id")
* CPU identification for machine, and clock frequency (in case of overclocking)
* CPU cache sizes (L1/L2/L3)
* Whether or not CPU throttling is enabled (if it can be easily determined)
* RAM size
* GPU identification (if any)
* Benchmark unique name
* Programming language(s) associated with benchmark (e.g. a benchmark
may involve both C++ and Python)
* Benchmark time, plus mean and standard deviation if available, else NULL

see discussion on mailing list https://lists.apache.org/thread.html/278e573445c83bbd8ee66474b9356c5291a16f6b6eca11dbbe4b473a@%3Cdev.arrow.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)