fix pages

.github/workflows/static.yml

@@ -0,0 +1,53 @@
+# Simple workflow for deploying static content to GitHub Pages
+name: Deploy static content to Pages
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["main"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  pages-directory-listing:
+    runs-on: ubuntu-latest
+    name: Directory Listings Index
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v4
+
+      - name: Generate Directory Listings
+        uses: jayanta525/[email protected]
+        with:
+          FOLDER: data
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v4
+        with:
+          path: 'data'
+
+  deploy:
+    needs: pages-directory-listing
+
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

README.md

@@ -12,5 +12,28 @@ cargo bench
 cargo run --release --package cuprate-benchmark --features all
 ```
 
-## Results
-See `/docs` or <https://benches.hinto.rs> for historical benchmark data.
+## Data
+See `/data` or <https://benches.hinto.rs> for historical benchmark data.
+
+### Directory structure
+```
+data/
+└── $MACHINE_NAME/
+    ├── criterion/
+    │   └── $COMMIT_1..$COMMIT_2/
+    │       └── $CRITERION_DATA
+    └── benchmarks/
+        └── $COMMIT/
+            └── $BENCHMARKING_DATA
+```
+
+- The top-level directories are named after the machines being used
+- Each top-level directory have 2 sub-directories: `criterion` and `benchmarks`
+- Within `criterion`, the data is placed in directories with the `Cuprate/cuprate` commits being compared
+- Within `benchmarks`, the data is placed in directories with the `Cuprate/cuprate` commit used
+
+### Machines
+
+| Machine name/directory | CPU                    | Core/thread count | Memory | Disk |
+|------------------------|------------------------|-------------------|--------|------|
+| moo                    | Intel Xeon E5 2698 v3  | 8/16              | 32 GB  | NVMe SSD