Repository size is very large about duckdb-web HOT 3 CLOSED

Yes, this was from a time when we used to have a script that auto-committed benchmark results to this repository. They definitely should be cleaned up as this history is unnecessarily clogging the repo.

from duckdb-web.

+1

Just came here to open this issue. I wanted to help a bit with documentation but cloning a 1.2GB repo for a casual PR is a hindrance. Thanks for the depth 1 workaround.

from duckdb-web.

I have cleaned up the repo now, it's now down to 75MB. I ended up running the following deletion commands:

bfg --delete-files minibenchmarks.db
bfg --delete-folders benchmark_logs
bfg --delete-folders benchmark_results
bfg --delete-folders individual_results
bfg --delete-files "*-stdout.html"
bfg --delete-files "*-stderr.html"
bfg --delete-files "*-graph.html"
bfg --delete-files "*-results.csv"
bfg --delete-folders benchmarking
bfg --delete-files benchmark-info.json
bfg --delete-folders coverage
bfg --delete-folders graphs

from duckdb-web.