You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .autoloop/programs/perf-comparison/program.md
+14-49Lines changed: 14 additions & 49 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This is an open-ended program — it runs continuously, always adding the next b
24
24
- Outputs the same JSON format
25
25
5.**Update `playground/benchmarks.html`** if needed to display the new function's comparison metrics.
26
26
27
-
The evaluation step (below) runs `benchmarks/run_benchmarks.sh`to execute **every**TS/Python benchmark pair and regenerates `benchmarks/results.json` with the real timing data. That regenerated file is what gets committed on a successful iteration, so when the autoloop branch is merged to `main`, the pages workflow (`.github/workflows/pages.yml`) picks up the real results and `playground/benchmarks.html`renders real comparison data instead of "No benchmark data available yet."
27
+
The autoloop iteration only needs to add the benchmark scripts; it does **not**need to run them or update `benchmarks/results.json`. The pages workflow (`.github/workflows/pages.yml`) executes `benchmarks/run_benchmarks.sh`on every push to `main` and publishes the regenerated `results.json` to the playground site, so real benchmark data appears on `playground/benchmarks.html`once the autoloop branch is merged.
28
28
29
29
### Key constraints
30
30
@@ -50,58 +50,23 @@ Do NOT modify:
50
50
51
51
## Evaluation
52
52
53
-
The evaluation runs `benchmarks/run_benchmarks.sh`, which executes every TS/Python
54
-
benchmark pair and writes real timing data to `benchmarks/results.json`. The metric
55
-
is the number of benchmarks that appear in that regenerated file — i.e. the number
56
-
of function pairs whose benchmarks actually ran to completion and produced valid
57
-
JSON output. This means a benchmark pair is only "counted" if it truly runs, and
58
-
the committed `benchmarks/results.json` always reflects real data that the
59
-
`pages.yml` workflow will copy to the playground on merge to `main`.
0 commit comments