Open patrick-ogrady opened 1 year ago
https://github.com/ava-labs/avalanchego/pull/1278
During hypersdk load testing, I found that avalanchego spends the majority of time performing compression-related tasks (zstd should help a ton here):
hypersdk
avalanchego
zstd
Showing nodes accounting for 16600ms, 71.55% of 23200ms total Dropped 486 nodes (cum <= 116ms) Showing top 10 nodes out of 233 flat flat% sum% cum cum% 3040ms 13.10% 13.10% 7990ms 34.44% compress/flate.(*compressor).deflate 2500ms 10.78% 23.88% 3170ms 13.66% compress/flate.(*decompressor).huffSym 2160ms 9.31% 33.19% 2160ms 9.31% runtime.memmove 1820ms 7.84% 41.03% 1820ms 7.84% crypto/sha256.block 1730ms 7.46% 48.49% 1730ms 7.46% runtime/internal/syscall.Syscall6 1550ms 6.68% 55.17% 1670ms 7.20% github.com/golang/snappy.encodeBlock 1460ms 6.29% 61.47% 2290ms 9.87% compress/flate.(*compressor).findMatch 820ms 3.53% 65.00% 820ms 3.53% compress/flate.matchLen (inline) 760ms 3.28% 68.28% 760ms 3.28% compress/flate.(*dictDecoder).writeByte 760ms 3.28% 71.55% 760ms 3.28% runtime.memclrNoHeapPointers
This issue has become stale because it has been open 60 days with no activity. Adding the lifecycle/frozen label will exempt this issue from future lifecycle events.
lifecycle/frozen
https://github.com/ava-labs/avalanchego/pull/1278
During
hypersdk
load testing, I found thatavalanchego
spends the majority of time performing compression-related tasks (zstd
should help a ton here):