- Use 1200px as website width, and make it a 3-column layout.
- Switch graphs to log y scale, and show 0.2x to 5x by default.
ApexCharts currently struggles with log y scales, glitches with outliers
(at least in Safari), and does not support extensive graph interaction
(like double clicking traces to isolate, and the toolbar).
- Always use relative values to display benchmarks
(actual values are platform dependent and meaningless).
- Use the median of the last 10 values as middle, such that new benchmarks
are always on the graph.
- Don't round values in the data aggregator, round them on visualization
instead.
- Use toolbar in detail charts.
- Don't use shared tooltip.
Previously, ticks on the x-axis are currently positioned perfectly sequentially.
This can skew results when timing between samples is inconsistent.
This graphing bug partially explained some jumps in the current graphs.
---------
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
This provides a web interface generated with Hugo for tracking
benchmark results over time. Automatic dark theme support is
provided using water.css.
Benchmarks are run daily on a dedicated server with the `master` branch
of Godot compiled from source on that server, so that build time and
memory usage during the build can also be tracked over time.
Binary size as well as startup/shutdown time and memory usage
from an empty project are also measured.
