[ARROW-4313] Define general benchmark database schema

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Component/s: Benchmarking
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/20885
• Assignee: Tanya Schlusser
• Reporter: Wes McKinney
• Created: 21/Jan/19 17:14
• Updated: 11/Jan/23 07:33
• Resolved: 27/Feb/19 14:18

Description

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

Issue Links

• is related to: ARROW-4354 Explore Codespeed feasibility and ease of customization
• links to: GitHub Pull Request #3586