feat: IPC transport (UNIX domain socket) #76
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Warning: this is a breaking API change. -> No it's not after #78!
Added the IPC transport type, backed by
tokio::net::UnixStream
. This required an abstraction over theTransport
address type, which is now handled by a traitAddress
:This is because IPC sockets bind to actual filesystem paths rather than IP addresses.
For this reason, now most sockets have a generic
Transport<A: Address>
impl block, plus an impl with theTransport<SocketAddr>
concrete type and same forTransport<PathBuf>
.Benchmarks
Added benchmarks to our criterion suite. Here are a few interesting results:
Interestingly, with the current implementation IPC has a much higher throughput with smaller messages, while TCP is a bit faster with bigger messages.
This is a 2.4x increase for small messages!
Related links: