You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Osmosis, since our upgrade to SDK v50, we have found that baseapp.GetLastBlockHeight has caused significant performance degredation in the mempool.
This is coming from Skip's BlockSDK using GetLastBlockHeight internally, and baseapp using a method that requires re-computing the hash. This is quite easily mitigated performance-wise SDK side, by making the store Committer interface provide a GetLastVersion method, in addition to GetLastCommitInfo method.
Or alternatively, make the store interfaces cache the last CommitInfo rather than re-computing the hash every time.
Problem Definition
No response
Proposed Feature
Either:
Make the Committer interface have a GetLastVersion field
Make rootmulti store cache the LastCommitID and not re-compute the hash every time.
The text was updated successfully, but these errors were encountered:
Summary
In Osmosis, since our upgrade to SDK v50, we have found that baseapp.GetLastBlockHeight has caused significant performance degredation in the mempool.
This is coming from Skip's BlockSDK using
GetLastBlockHeight
internally, and baseapp using a method that requires re-computing the hash. This is quite easily mitigated performance-wise SDK side, by making the storeCommitter
interface provide aGetLastVersion
method, in addition toGetLastCommitInfo
method.Or alternatively, make the store interfaces cache the last CommitInfo rather than re-computing the hash every time.
Problem Definition
No response
Proposed Feature
Either:
The text was updated successfully, but these errors were encountered: