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
You know what's better than deduplication (#117)? Not hitting up the db for literally everything.
It isn't a particularly big stretch to assume that most of the queries will want information that is recent. A lot of the requests can omit hitting up the database if the gateway maintained a small cache of the n-most recent blocks (along with hashes and other metadata). As each gateway is currently (See: #84) stuck indexing everything, the cache can be updated as it indexes as well.
In the future, instances that do not have an indexer could either use a scanning-tolerant cache replacement policy, or use the same logic as long as the gateway always has an idea of what the most recently indexed block is.
The text was updated successfully, but these errors were encountered:
You know what's better than deduplication (#117)? Not hitting up the db for literally everything.
It isn't a particularly big stretch to assume that most of the queries will want information that is recent. A lot of the requests can omit hitting up the database if the gateway maintained a small cache of the n-most recent blocks (along with hashes and other metadata). As each gateway is currently (See: #84) stuck indexing everything, the cache can be updated as it indexes as well.
In the future, instances that do not have an indexer could either use a scanning-tolerant cache replacement policy, or use the same logic as long as the gateway always has an idea of what the most recently indexed block is.
The text was updated successfully, but these errors were encountered: