Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fixed a typo #337

Merged
merged 1 commit into from
Jan 8, 2024
+1 −1
Merged

fixed a typo #337

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/intraprocess_communication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ The executor can then pop the message from the buffer and trigger the callback o
The choice of having independent buffers for each `Subscription` leads to the following advantages:

- It is easy to support different QoS for each `Subscription`, while, at the same time, simplifying the implementation.
- Multiple `Subscription`s can extract messages from their own buffer in parallel without blocking each other, thus providing an higher throughput.
- Multiple `Subscription`s can extract messages from their own buffer in parallel without blocking each other, thus providing higher throughput.

The only drawback is that the system is not reusing as much resources as possible, compared to sharing buffers between entities.
However, from a practical point of view, the memory overhead caused by the proposed implementation with respect to the current one, will always be only a tiny delta compared to the overall memory usage of the application.
Expand Down