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
I floated this idea when we were trying to shut down a room and it took a while because it has to run state resolution after sending each event.
Instead of sending each event in a sequence one-by-one, can we come up with a scheme that sends a chain of events, such that all of them (except the first) have prev_events=[the previous one] and then make use of this in situations where we know we need to send multiple events?
This may help for:
batch sending (batch import of history)?
unsure if any work has already been done here to improve performance
shutdown rooms / mass leaves
room creation (there are a few events to be sent at once)
room upgrades?
and possibly others...
Edit: can't remember if there was an issue already open for this and can't dig it up, sorry if it's a duplicate.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #12010.
I floated this idea when we were trying to shut down a room and it took a while because it has to run state resolution after sending each event.
Instead of sending each event in a sequence one-by-one, can we come up with a scheme that sends a chain of events, such that all of them (except the first) have
prev_events=[the previous one]
and then make use of this in situations where we know we need to send multiple events?This may help for:
and possibly others...
Edit: can't remember if there was an issue already open for this and can't dig it up, sorry if it's a duplicate.
The text was updated successfully, but these errors were encountered: