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
Right now, in subscribeRepos, we query the datastore separately for each connected subscriber (client). This is fine for historical blocks, but it's duplicative for new blocks. For ongoing subscribers, ideally we should only do a given datastore query once, and then fan out the results to all subscribers.
This would take a bit of rearchitecting. Right now, we do all of this inside the request handler, per client:
We'd need to start a separate, shared thread for the realtime datastore queries, collect the resulting blocks into events in memory, and have each client's request handler read and emit from there.
The text was updated successfully, but these errors were encountered:
Right now, in
subscribeRepos
, we query the datastore separately for each connected subscriber (client). This is fine for historical blocks, but it's duplicative for new blocks. For ongoing subscribers, ideally we should only do a given datastore query once, and then fan out the results to all subscribers.This would take a bit of rearchitecting. Right now, we do all of this inside the request handler, per client:
arroba/arroba/xrpc_sync.py
Lines 199 to 206 in 351d43f
We'd need to start a separate, shared thread for the realtime datastore queries, collect the resulting blocks into events in memory, and have each client's request handler read and emit from there.
The text was updated successfully, but these errors were encountered: