Perf demo added (including to pipeline): classic capnp copy vs Flow-IPC zero-copy. / capnp problem work-around. / Tweaked API. / Tweaks. #78
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… `wait` until the server exits and ensure it yielded 0.
…to make a hookier, simpler intro to Flow-IPC: I wanted a basic comparison to demonstrate (primarily) perf benefits of our core (but not only) use-case/API, SHM-backed zero-copy capnp-data transmission; and (secondarily) coding-convenience benefits of same. So I wrote this perf_demo test which compares vanilla-capnp use with IPC via local-socket with copy-in and copy-out versus Flow-IPC SHM-backed zero-copy capnp-ing. It is not comprehensive, but it is a nice start at least and will provide some benchmarks to quote in aforementioned Flow-IPC intro.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.