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
Can we keep this value locally written to a file (e..g we cache all address / osmo amount pairs), and when this query is needed, we first return the local value, and then later get it from cache.
Also perhaps we should just do a direct RPC or SQS call to get a user's osmo amount, since this query is oddly slow on edge.
The text was updated successfully, but these errors were encountered:
In network traces, I routinely see the following query taking 800ms, and appearing to block things about page load. Faster refreshes get 300ms.
Can we keep this value locally written to a file (e..g we cache all address / osmo amount pairs), and when this query is needed, we first return the local value, and then later get it from cache.
Also perhaps we should just do a direct RPC or SQS call to get a user's osmo amount, since this query is oddly slow on edge.
The text was updated successfully, but these errors were encountered: