499109b165
validateWorker() reads from validateQ and invokes validate function that performs validation of the message. Signature validation is performed synchronously. The number of validate workers defaults to the number of CPUs and can be updated with WithValidateWorkers function. With no additional user validators, signature validation is the bottleneck when receiving new messages. Increasing the number of validating workers does not help given the context switching and bottleneck nature of this spot. As stated in WithValidateWorkers documentation, this function should be used rather to limit the number of workers to devote less CPU time for synchronous validation. On the other hand, with the default size of `validateQ`, some applications built on a top of libp2p may experience throttled validation and lost messages. This problem is addressed by WithValidateQueueSize allowing to configure the buffer size for synchronous validation. Application developers knowing the nature of their protocols can set this value to minimise the possibility of throttled synchronous validation and dropped messages. Configurable buffer size allows to gracefully handle peaks of messages and, from the other side, the number of concurrent synchronous workers is still limited by validateWorkers property so the receiver should not get congested. |
||
---|---|---|
pb | ||
.gitignore | ||
.travis.yml | ||
LICENSE | ||
README.md | ||
blacklist.go | ||
blacklist_test.go | ||
codecov.yml | ||
comm.go | ||
discovery.go | ||
discovery_test.go | ||
doc.go | ||
floodsub.go | ||
floodsub_test.go | ||
go.mod | ||
go.sum | ||
gossipsub.go | ||
gossipsub_test.go | ||
mcache.go | ||
mcache_test.go | ||
notify.go | ||
pubsub.go | ||
randomsub.go | ||
sign.go | ||
sign_test.go | ||
subscription.go | ||
topic.go | ||
topic_test.go | ||
trace.go | ||
tracer.go | ||
validation.go |
README.md
go-libp2p-pubsub
A pubsub system with flooding and gossiping variants.
This is the canonical pubsub implementation for libp2p.
We currently provide three implementations:
- floodsub, which is the baseline flooding protocol.
- gossipsub, which is a more advanced router with mesh formation and gossip propagation. See spec and implementation for more details.
- randomsub, which is a simple probabilistic router that propagates to random subsets of peers.
Table of Contents
Install
go get github.com/libp2p/go-libp2p-pubsub
Usage
To be used for messaging in p2p instrastructure (as part of libp2p) such as IPFS, Ethereum, other blockchains, etc.
Implementations
See libp2p/specs/pubsub#Implementations.
Documentation
See the libp2p specs for high level documentation and godoc for API documentation.
Tracing
The pubsub system supports tracing, which collects all events pertaining to the internals of the system. This allows you to recreate the complete message flow and state of the system for analysis purposes.
To enable tracing, instantiate the pubsub system using the WithEventTracer
option; the option
accepts a tracer with three available implementations in-package (trace to json, pb, or a remote peer).
If you want to trace using a remote peer, you can do so using the traced
daemon from go-libp2p-pubsub-tracer. The package also includes a utility program, tracestat
, for analyzing the traces collected by the daemon.
For instance, to capture the trace as a json file, you can use the following option:
pubsub.NewGossipSub(..., pubsub.NewEventTracer(pubsub.NewJSONTracer("/path/to/trace.json")))
To capture the trace as a protobuf, you can use the following option:
pubsub.NewGossipSub(..., pubsub.NewEventTracer(pubsub.NewPBTracer("/path/to/trace.pb")))
Finally, to use the remote tracer, you can use the following incantations:
// assuming that your tracer runs in x.x.x.x and has a peer ID of QmTracer
pi, err := peer.AddrInfoFromP2pAddr(ma.StringCast("/ip4/x.x.x.x/tcp/4001/p2p/QmTracer"))
if err != nil {
panic(err)
}
tracer, err := pubsub.NewRemoteTracer(ctx, host, pi)
if err != nil {
panic(err)
}
ps, err := pubsub.NewGossipSub(..., pubsub.WithEventTracer(tracer))
Contribute
Contributions welcome. Please check out the issues.
Check out our contributing document for more information on how we work, and about contributing in general. Please be aware that all interactions related to multiformats are subject to the IPFS Code of Conduct.
Small note: If editing the README, please conform to the standard-readme specification.
License
MIT © Jeromy Johnson
The last gx published version of this module was: 0.11.16: QmfB4oDUTiaGEqT13P1JqCEhqW7cB1wpKtq3PP4BN8PhQd