Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Introduce prefixed storage with enumeration #4185
Iteration on overlay by changing Hashmap to BTreeMap:
Early benchmark between BTreeMap and HashMap:
if maps contain less than 10_000 key/values then performance are quite same.
Iteration on overlay with cache.
If ext_call specifies the range on which it will iterate
If ext_call doesn't specifies the range on which it will iterate
then the only way to make a cache that is useful is to reduce the cache to the not dirty part when the storage gets dirty.
The PRs waiting for this are no longer waiting, but it seems a very useful feature. About the deadline, it is mostly about if performance are OK by switching HashMap to BTreeMap, or if we need better and different cache and still use HashMap
hmm then maybe it worth making the sr-io API
EDIT: top description updated including this thought
Shortly after this goes in we will want to consider adding to storage