mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-06-25 13:01:09 +00:00
80616f6d03
[litep2p](https://github.com/altonen/litep2p) is a libp2p-compatible P2P networking library. It supports all of the features of `rust-libp2p` that are currently being utilized by Polkadot SDK. Compared to `rust-libp2p`, `litep2p` has a quite different architecture which is why the new `litep2p` network backend is only able to use a little of the existing code in `sc-network`. The design has been mainly influenced by how we'd wish to structure our networking-related code in Polkadot SDK: independent higher-levels protocols directly communicating with the network over links that support bidirectional backpressure. A good example would be `NotificationHandle`/`RequestResponseHandle` abstractions which allow, e.g., `SyncingEngine` to directly communicate with peers to announce/request blocks. I've tried running `polkadot --network-backend litep2p` with a few different peer configurations and there is a noticeable reduction in networking CPU usage. For high load (`--out-peers 200`), networking CPU usage goes down from ~110% to ~30% (80 pp) and for normal load (`--out-peers 40`), the usage goes down from ~55% to ~18% (37 pp). These should not be taken as final numbers because: a) there are still some low-hanging optimization fruits, such as enabling [receive window auto-tuning](https://github.com/libp2p/rust-yamux/pull/176), integrating `Peerset` more closely with `litep2p` or improving memory usage of the WebSocket transport b) fixing bugs/instabilities that incorrectly cause `litep2p` to do less work will increase the networking CPU usage c) verification in a more diverse set of tests/conditions is needed Nevertheless, these numbers should give an early estimate for CPU usage of the new networking backend. This PR consists of three separate changes: * introduce a generic `PeerId` (wrapper around `Multihash`) so that we don't have use `NetworkService::PeerId` in every part of the code that uses a `PeerId` * introduce `NetworkBackend` trait, implement it for the libp2p network stack and make Polkadot SDK generic over `NetworkBackend` * implement `NetworkBackend` for litep2p The new library should be considered experimental which is why `rust-libp2p` will remain as the default option for the time being. This PR currently depends on the master branch of `litep2p` but I'll cut a new release for the library once all review comments have been addresses. --------- Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> Co-authored-by: Dmitry Markin <dmitry@markin.tech> Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com> Co-authored-by: Alexandru Vasile <alexandru.vasile@parity.io>
174 lines
5.8 KiB
Rust
174 lines
5.8 KiB
Rust
// This file is part of Substrate.
|
|
|
|
// Copyright (C) Parity Technologies (UK) Ltd.
|
|
// SPDX-License-Identifier: GPL-3.0-or-later WITH Classpath-exception-2.0
|
|
|
|
// This program is free software: you can redistribute it and/or modify
|
|
// it under the terms of the GNU General Public License as published by
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
// (at your option) any later version.
|
|
|
|
// This program is distributed in the hope that it will be useful,
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
// GNU General Public License for more details.
|
|
|
|
// You should have received a copy of the GNU General Public License
|
|
// along with this program. If not, see <https://www.gnu.org/licenses/>.
|
|
|
|
#![warn(missing_docs)]
|
|
#![recursion_limit = "1024"]
|
|
|
|
//! Substrate authority discovery.
|
|
//!
|
|
//! This crate enables Substrate authorities to discover and directly connect to
|
|
//! other authorities. It is split into two components the [`Worker`] and the
|
|
//! [`Service`].
|
|
//!
|
|
//! See [`Worker`] and [`Service`] for more documentation.
|
|
|
|
pub use crate::{
|
|
error::Error,
|
|
service::Service,
|
|
worker::{AuthorityDiscovery, NetworkProvider, Role, Worker},
|
|
};
|
|
|
|
use std::{collections::HashSet, sync::Arc, time::Duration};
|
|
|
|
use futures::{
|
|
channel::{mpsc, oneshot},
|
|
Stream,
|
|
};
|
|
|
|
use sc_network::{event::DhtEvent, Multiaddr};
|
|
use sc_network_types::PeerId;
|
|
use sp_authority_discovery::AuthorityId;
|
|
use sp_blockchain::HeaderBackend;
|
|
use sp_runtime::traits::Block as BlockT;
|
|
|
|
mod error;
|
|
mod interval;
|
|
mod service;
|
|
mod worker;
|
|
|
|
#[cfg(test)]
|
|
mod tests;
|
|
|
|
/// Configuration of [`Worker`].
|
|
pub struct WorkerConfig {
|
|
/// The maximum interval in which the node will publish its own address on the DHT.
|
|
///
|
|
/// By default this is set to 1 hour.
|
|
pub max_publish_interval: Duration,
|
|
|
|
/// Interval at which the keystore is queried. If the keys have changed, unconditionally
|
|
/// re-publish its addresses on the DHT.
|
|
///
|
|
/// By default this is set to 1 minute.
|
|
pub keystore_refresh_interval: Duration,
|
|
|
|
/// The maximum interval in which the node will query the DHT for new entries.
|
|
///
|
|
/// By default this is set to 10 minutes.
|
|
pub max_query_interval: Duration,
|
|
|
|
/// If `false`, the node won't publish on the DHT multiaddresses that contain non-global
|
|
/// IP addresses (such as 10.0.0.1).
|
|
///
|
|
/// Recommended: `false` for live chains, and `true` for local chains or for testing.
|
|
///
|
|
/// Defaults to `true` to avoid the surprise factor.
|
|
pub publish_non_global_ips: bool,
|
|
|
|
/// Public addresses set by the node operator to always publish first in the authority
|
|
/// discovery DHT record.
|
|
pub public_addresses: Vec<Multiaddr>,
|
|
|
|
/// Reject authority discovery records that are not signed by their network identity (PeerId)
|
|
///
|
|
/// Defaults to `false` to provide compatibility with old versions
|
|
pub strict_record_validation: bool,
|
|
}
|
|
|
|
impl Default for WorkerConfig {
|
|
fn default() -> Self {
|
|
Self {
|
|
// Kademlia's default time-to-live for Dht records is 36h, republishing records every
|
|
// 24h through libp2p-kad. Given that a node could restart at any point in time, one can
|
|
// not depend on the republishing process, thus publishing own external addresses should
|
|
// happen on an interval < 36h.
|
|
max_publish_interval: Duration::from_secs(1 * 60 * 60),
|
|
keystore_refresh_interval: Duration::from_secs(60),
|
|
// External addresses of remote authorities can change at any given point in time. The
|
|
// interval on which to trigger new queries for the current and next authorities is a
|
|
// trade off between efficiency and performance.
|
|
//
|
|
// Querying 700 [`AuthorityId`]s takes ~8m on the Kusama DHT (16th Nov 2020) when
|
|
// comparing `authority_discovery_authority_addresses_requested_total` and
|
|
// `authority_discovery_dht_event_received`.
|
|
max_query_interval: Duration::from_secs(10 * 60),
|
|
publish_non_global_ips: true,
|
|
public_addresses: Vec::new(),
|
|
strict_record_validation: false,
|
|
}
|
|
}
|
|
}
|
|
|
|
/// Create a new authority discovery [`Worker`] and [`Service`].
|
|
///
|
|
/// See the struct documentation of each for more details.
|
|
pub fn new_worker_and_service<Client, Block, DhtEventStream>(
|
|
client: Arc<Client>,
|
|
network: Arc<dyn NetworkProvider>,
|
|
dht_event_rx: DhtEventStream,
|
|
role: Role,
|
|
prometheus_registry: Option<prometheus_endpoint::Registry>,
|
|
) -> (Worker<Client, Block, DhtEventStream>, Service)
|
|
where
|
|
Block: BlockT + Unpin + 'static,
|
|
Client: AuthorityDiscovery<Block> + Send + Sync + 'static + HeaderBackend<Block>,
|
|
DhtEventStream: Stream<Item = DhtEvent> + Unpin,
|
|
{
|
|
new_worker_and_service_with_config(
|
|
Default::default(),
|
|
client,
|
|
network,
|
|
dht_event_rx,
|
|
role,
|
|
prometheus_registry,
|
|
)
|
|
}
|
|
|
|
/// Same as [`new_worker_and_service`] but with support for providing the `config`.
|
|
///
|
|
/// When in doubt use [`new_worker_and_service`] as it will use the default configuration.
|
|
pub fn new_worker_and_service_with_config<Client, Block, DhtEventStream>(
|
|
config: WorkerConfig,
|
|
client: Arc<Client>,
|
|
network: Arc<dyn NetworkProvider>,
|
|
dht_event_rx: DhtEventStream,
|
|
role: Role,
|
|
prometheus_registry: Option<prometheus_endpoint::Registry>,
|
|
) -> (Worker<Client, Block, DhtEventStream>, Service)
|
|
where
|
|
Block: BlockT + Unpin + 'static,
|
|
Client: AuthorityDiscovery<Block> + 'static,
|
|
DhtEventStream: Stream<Item = DhtEvent> + Unpin,
|
|
{
|
|
let (to_worker, from_service) = mpsc::channel(0);
|
|
|
|
let worker =
|
|
Worker::new(from_service, client, network, dht_event_rx, role, prometheus_registry, config);
|
|
let service = Service::new(to_worker);
|
|
|
|
(worker, service)
|
|
}
|
|
|
|
/// Message send from the [`Service`] to the [`Worker`].
|
|
pub(crate) enum ServicetoWorkerMsg {
|
|
/// See [`Service::get_addresses_by_authority_id`].
|
|
GetAddressesByAuthorityId(AuthorityId, oneshot::Sender<Option<HashSet<Multiaddr>>>),
|
|
/// See [`Service::get_authority_ids_by_peer_id`].
|
|
GetAuthorityIdsByPeerId(PeerId, oneshot::Sender<Option<HashSet<AuthorityId>>>),
|
|
}
|