Perf demo added (including to pipeline): classic capnp copy vs Flow-IPC zero-copy. / capnp problem work-around. / Tweaked API. / Tweaks. #78
Commits on Mar 1, 2024
Commits on Mar 2, 2024
-
-
-
Opportunistic: Even for the simple link-tests, pipeline should really…
… `wait` until the server exits and ensure it yielded 0.
Commits on Mar 3, 2024
-
(Explaining preceding WIP commits and this one) Inspired by attempts …
…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.
-
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.