osmosis
osmosis copied to clipboard
[Perf]: Understand why cosmwasm.StoreCode is so slow
Summary
Looking at CPU profiles of our tests, cosmwasm code storage seems surprisingly slow. We should definitely sanity check that its not that our tests are doing a lot of StoreCode calls, but it does preliminarily look were offloading much more logic to C / Rust than we should, and that this is slower than it should be.
One way to look into this is osmosis/x/cosmwasmpool$ go test -v . -cpuprofile=cpu.out and go tool pprof -http=: cpu.out.
I wonder if analyze code can be done in native golang?
Problem Definition
.
Proposed Feature
Aim to speedup cosmwasm code storage. Hopefully this is instructive for general cosmwasm bottlenecks we face.