Skip to content

Conversation

@kaimast
Copy link
Collaborator

@kaimast kaimast commented Dec 8, 2025

This PR cleans up the benchmark page, that has become hard to search through. To preview the changes, you can check out this branch (dev/remove-benchmark-noise) and then open dev/bench/index.html.

Changes:

  • Removes all data from before 2024. Right now, some graphs have 1000s of data points, making it hard to read them and slows down render time. The old data is still in the git history, so no information is lost.
  • Add a header element to the benchmark page, so that you can search for a specific graph using Ctrl+F
  • Made the graphs slightly wider (95% instead of 1000px)

@kaimast kaimast marked this pull request as ready for review December 8, 2025 18:34
@kaimast kaimast requested a review from raychu86 December 8, 2025 18:34
@raychu86
Copy link
Collaborator

raychu86 commented Dec 8, 2025

I do not like removing old data outright; I also consider that data only in git history is effectively lost because nobody will dig it up (and will not know that it even exists).

Is there a way to remove remove old benchmark data in a way that we still see the gist it? So we remove most runs, but keep a datapoint from a run that happened every month or so

@kaimast kaimast force-pushed the dev/remove-benchmark-noise branch from 9fceef8 to ef5b3bc Compare January 5, 2026 22:53
@kaimast kaimast force-pushed the dev/remove-benchmark-noise branch from ef5b3bc to 41fcd74 Compare January 6, 2026 05:04
@kaimast
Copy link
Collaborator Author

kaimast commented Jan 6, 2026

@raychu86 I changed the PR to include a simple vibe-coded UI that lets you select a time range. This way, we do not need to remove any data.

@kaimast kaimast merged commit 6831e2f into gh-pages Jan 6, 2026
@kaimast kaimast deleted the dev/remove-benchmark-noise branch January 6, 2026 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants