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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
At the moment, calling NetworkService::write_notifications synchronously verifies whether we have a connection with the peer, and if so sends a message on a channel in destination to the background task of this specific peer.
The problem is that this channel is already quite overloaded, and we should ideally try to reduce the traffic on this point of contention.
Additionally, we can't properly implement #5481 with this system.
Instead, there should be a field in NetworkService (notNetworkWorker) that directly contains channels whose receiving side are the background tasks.
The text was updated successfully, but these errors were encountered:
At the moment, calling
NetworkService::write_notifications
synchronously verifies whether we have a connection with the peer, and if so sends a message on a channel in destination to the background task of this specific peer.The problem is that this channel is already quite overloaded, and we should ideally try to reduce the traffic on this point of contention.
Additionally, we can't properly implement #5481 with this system.
Instead, there should be a field in
NetworkService
(notNetworkWorker
) that directly contains channels whose receiving side are the background tasks.The text was updated successfully, but these errors were encountered: