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
The cache works great, BUT we are currently clearing the entire cache at the start of a new scan. This causes a spike in db queries at the start of every scan. It also causes ble_obs to all cluster around the start of a scan aggrevating db latency.
Instead we should selectively crawl and clear the cache instead. This will help more equally distribute db access.
Should also track an accurate cache size, this essentially is the backlog of queries. Then track a completed queries count.
The text was updated successfully, but these errors were encountered:
The cache works great, BUT we are currently clearing the entire cache at the start of a new scan. This causes a spike in db queries at the start of every scan. It also causes
ble_obs
to all cluster around the start of a scan aggrevating db latency.Instead we should selectively crawl and clear the cache instead. This will help more equally distribute db access.
Should also track an accurate cache size, this essentially is the backlog of queries. Then track a completed queries count.
The text was updated successfully, but these errors were encountered: