Add rpcCacheCapacity
option to ApiOptions
#6020
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ApiPromise
options (ApiOptions
) now has support forrpcCacheCapacity
. This will allow the ability to set the size of the cache inRpcCore
.This use to be infinite but for long standing instances where the api is used, this was terrible for memory, therefore we added an internal TTL for the LRUCache in #5997. But that PR also changed the storage cache for rpc calls from a
Map
to an LRUCache, which needs a defined size. This PR aims to allow the user to define an escape hatch to not have to deal with the default size.