godotengine/godot-benchmarks
1
0
Fork 0
mirror of https://github.com/godotengine/godot-benchmarks.git synced 2025-12-31 09:49:13 +03:00
Code Issues Packages Projects Releases Wiki Activity
Files
d3425f06b3dd5b15732a66376f39343824445537
godot-benchmarks/web
History
Lukas Tenbrink d3425f06b3 General graphing updates: Median, normalization, rounding, tooltips, toolbar (#116) 
- 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.
2025-08-08 17:12:50 +02:00
..
content
Add web interface for tracking benchmark results over time (#59)
2024-04-18 15:53:55 +02:00
data
Improve docs and simplify/fix setup (#64)
2024-04-29 22:27:08 +02:00
godot-empty-project
Add web interface for tracking benchmark results over time (#59)
2024-04-18 15:53:55 +02:00
layouts
Add graphs for binary size, build time, build memory use, startup time, and memory use (#111)
2025-06-25 20:17:14 +02:00
src-data
Add graphs for binary size, build time, build memory use, startup time, and memory use (#111)
2025-06-25 20:17:14 +02:00
static
General graphing updates: Median, normalization, rounding, tooltips, toolbar (#116)
2025-08-08 17:12:50 +02:00
.gdignore
Add web interface for tracking benchmark results over time (#59)
2024-04-18 15:53:55 +02:00
generate-content.py
Improve docs and simplify/fix setup (#64)
2024-04-29 22:27:08 +02:00
hugo.toml
Add web interface for tracking benchmark results over time (#59)
2024-04-18 15:53:55 +02:00
README.md
Run benchmarks on NVIDIA GPU
2024-11-27 15:09:46 +01:00

README.md

Web interface for benchmark results

This website is built with the Hugo static site generator. It's designed to work exclusively with the run-benchmarks.sh script, which runs benchmarks on a dedicated server with various GPU models.

How it works

  • Using the run-benchmarks.sh script, benchmark data is collected and saved to a single JSON file for each engine commit, with 4 runs:
    • CPU (debug template)
    • CPU (release template)
    • GPU (AMD, release template)
    • GPU (Intel, release template)
    • GPU (NVIDIA, release template)
  • The produced results (as .json or .md) should be copied into the src-data/benchmarks folder.
  • The ./generate-content.py script produces .md files in the content folder, so that web pages can be generated for each graph and each benchmark.
  • Hugo is used to create a homepage listing recent benchmarked commits, plus a single page per engine commit. This allows linking to individual benchmarked commit in a future-proof way.
  • ApexCharts is used to draw graphs on the homepage.
  • Water.css is used to provide styling, including automatic dark theme support.

Building

Development

  • Create JSON data or fetch existing JSON data from the live website, and copy the JSON files into the src-data/benchmarks folder. Files should be named using format YYYY-MM-DD_hash.json where hash is a 9-character Git commit hash of the Godot build used (truncated from a full commit hash). The files can also have the .md extension (for backward compatibility), but they should still be JSON inside.
  • Run ./generate-content.py. This should create .md pages in both the content/benchmark and the content/graph folders.
  • Run hugo server.

Production

  • Follow the same steps as in the Development section above.
  • Run hugo --minify.