Database + Frontend Google-Benchmark results

We use G-benchmark a lot. Each project contains several to almost 100 benchmarks, which are run on various (Linux) servers with very different configurations. Unfortunately the historic data is not stored and we cannot easily see how certain code progresses over time after we install new drivers or when we (hopefully) improve the code. Getting the data in one place to export to a csv is also manual work. We therefore want to store the results in a database and have ways to browse projects and see the evolution over time and git-submits. G-benchmark can export to json, as shown on [login to view URL] The "context" in this json needs to be enriched with various other data as given in a project-specific config-file (any format) and run-specific info (like git-commit, the server-IP, versions of certain drivers, git-ID, etc). This json needs to be sent to a database. The frontend should contain: - dashboard with recent runs, listing the newest benchmarks per project. - line-graphs of results per benchmark per server. - search - show outliers (search-criteria configurable) - export of data (csv) - automated export of data (html) Each benchmark-server needs to be initiated in the database, and be updated if the hardware changes. A simple script should do. Security can be simple, by whitelisting ip-ranges. The database-design we already have, but probably needs some tuning. The choice of language is free, but we want to run it as a docker. We think the code can be quite minimal, if done in a smart way and libraries are used for the frontend. If we're happy with the results, we have various requirements for the second phase.