You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2018/11/22 00:01:00 UTC
[jira] [Created] (GEODE-6087) Explore the best way to store and
visualize performance data across many builds
Dan Smith created GEODE-6087:
--------------------------------
Summary: Explore the best way to store and visualize performance data across many builds
Key: GEODE-6087
URL: https://issues.apache.org/jira/browse/GEODE-6087
Project: Geode
Issue Type: New Feature
Components: benchmarks
Reporter: Dan Smith
We want to be able to notice performance regressions in geode and track down when they show up. We will want to add running the benchmarks into CI, storing the results, and visualizing them.
We should explore what the best way is to store and visualize the data from many benchmark runs.
A few storage possibilities:
* Store data as directories or zip files, maybe upload them somewhere?
* Store data in a relational database?
* Some combination of the two (derby/sqlite database per run, perhaps?)
Visualization options:
* A chart of relative throughput or latency vs. build number?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)