Skip to content

Actions: englacial/zagg

Actions

Lambda Benchmark (on demand)

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
lambda-benchmark-command.yml
426 workflow runs
426 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
add 88 south stress test shard + benchmark Lambda Benchmark (on demand) #428: Issue comment #148 (comment) created by espg
6s
6s
Rework benchmark matrix: sharded tdigest, inline-vs-sidecar, K=4, 4 GB Lambda Benchmark (on demand) #427: Issue comment #196 (comment) created by espg
7s
7s
Rework benchmark matrix: sharded tdigest, inline-vs-sidecar, K=4, 4 GB Lambda Benchmark (on demand) #426: Issue comment #196 (comment) created by espg
6s
6s
Claude Summary Tracking (June 2026) Lambda Benchmark (on demand) #425: Issue comment #50 (comment) created by espg
8s
8s
Rework benchmark matrix: sharded tdigest, inline-vs-sidecar, K=4, 4 GB Lambda Benchmark (on demand) #424: Pull request #196 labeled by espg
6s
6s
Rework benchmark matrix: sharded tdigest, inline-vs-sidecar, K=4, 4 GB Lambda Benchmark (on demand) #423: Pull request #196 labeled by espg
8s
8s
Follow-ons to #183: dispatcher-side shard-aware granule_workers, and function-size variants gated on utilization Lambda Benchmark (on demand) #422: Issue comment #184 (comment) created by espg
6s
6s
Sharded CSR writes issue a per-array metadata-op storm — upstream ask: a no-probe / batch array-creation path in zarr-python Lambda Benchmark (on demand) #421: Issue comment #189 (comment) created by espg
6s
6s
Rework benchmark matrix: sharded tdigest, inline-vs-sidecar, K=4, 4 GB Lambda Benchmark (on demand) #420: Issue comment #196 (comment) created by espg
7s
7s
Granule-level read concurrency: the worker's serial granule x group loop is the dominant read-wall term Lambda Benchmark (on demand) #419: Issue comment #180 (comment) created by espg
7s
7s
Full-coverage sidecar write-back (issue #190) Lambda Benchmark (on demand) #418: Pull request #195 labeled by espg
9s
9s
Full-coverage sidecar write-back (issue #190) Lambda Benchmark (on demand) #417: Issue comment #195 (comment) created by espg
5s
5s
Full-coverage sidecar write-back (issue #190) Lambda Benchmark (on demand) #416: Issue comment #195 (comment) created by espg
5s
5s
Full-coverage sidecar write-back (issue #190) Lambda Benchmark (on demand) #415: Pull request #195 labeled by espg
8s
8s
Skip zarr metadata consolidation by default (opt-in) Lambda Benchmark (on demand) #413: Pull request #193 labeled by espg
5s
5s
Sidecar write-back persists only the config's read set (lazy), not full ~1,055-dataset coverage Lambda Benchmark (on demand) #412: Issue comment #190 (comment) created by espg
5s
5s
Skip zarr metadata consolidation by default (opt-in) Lambda Benchmark (on demand) #411: Pull request #193 labeled by espg
5s
5s
Add total AOI wall + finalize to benchmark columns (issue #180) Lambda Benchmark (on demand) #410: Issue comment #192 (comment) created by espg
5s
5s
Sidecar write-back persists only the config's read set (lazy), not full ~1,055-dataset coverage Lambda Benchmark (on demand) #409: Issue comment #190 (comment) created by espg
8s
8s
Sharded CSR writes issue a per-array metadata-op storm — upstream ask: a no-probe / batch array-creation path in zarr-python Lambda Benchmark (on demand) #408: Issue comment #189 (comment) created by espg
8s
8s
Granule-level read concurrency: the worker's serial granule x group loop is the dominant read-wall term Lambda Benchmark (on demand) #407: Issue comment #180 (comment) created by espg
7s
7s
Granule-level read concurrency: the worker's serial granule x group loop is the dominant read-wall term Lambda Benchmark (on demand) #406: Issue comment #180 (comment) created by espg
6s
6s
Granule-level read concurrency: the worker's serial granule x group loop is the dominant read-wall term Lambda Benchmark (on demand) #405: Issue comment #180 (comment) created by espg
7s
7s
Granule-level read concurrency: the worker's serial granule x group loop is the dominant read-wall term Lambda Benchmark (on demand) #404: Issue comment #180 (comment) created by espg
8s
8s
Granule-level read concurrency: the worker's serial granule x group loop is the dominant read-wall term Lambda Benchmark (on demand) #403: Issue comment #180 (comment) created by espg
6s
6s