Skip to content

avoid allocating 16 hashmaps per transaction #40738

avoid allocating 16 hashmaps per transaction

avoid allocating 16 hashmaps per transaction #40738

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Triggered via pull request November 5, 2024 01:36
Status Success
Total duration 32m 52s
Artifacts

execution-performance.yaml

on: pull_request
execution-performance  /  test-target-determinator
5m 26s
execution-performance / test-target-determinator
execution-performance  /  single-node-performance
23m 15s
execution-performance / single-node-performance
Fit to window
Zoom out
Zoom in