### **Benchmark Output Improvements and Bleeding-Edge AlaSQL Support** #### **1. DETAILED RESULTS table** * Keep the results table in markdown. * List versions vertically. * Use each test as its own column. * Move the ops/s label into the first column - for example: `v4.9.1 ops/s`. * Each test value must be an integer with no commas or dots. * Add a new column named **total** showing the sum of all test values for each version. #### **2. SUMMARY - Average Operations per Second by Version** * Values must be plain integers with no commas or dots. * Remove `ops/s` from the values. #### **3. Bleeding-edge AlaSQL version** * Add support for benchmarking the latest AlaSQL code from the GitHub repo: [https://github.com/AlaSQL/alasql](https://github.com/AlaSQL/alasql) * The repo has no built dist, so the workflow needs to pull the repo (e.g. as a submodule), build it, and then benchmark that build. #### **4. Cycles flag** * Replace `--quick` with a new flag named `--cycles`. * The flag sets how many cycles to run. * When not provided, default to the current non-quick behaviour.
Benchmark Output Improvements and Bleeding-Edge AlaSQL Support
1. DETAILED RESULTS table
v4.9.1 ops/s.2. SUMMARY - Average Operations per Second by Version
ops/sfrom the values.3. Bleeding-edge AlaSQL version
https://github.com/AlaSQL/alasql
4. Cycles flag
--quickwith a new flag named--cycles.