From f76e0619a025fa2a211671c0a4d311c1fbe88a61 Mon Sep 17 00:00:00 2001 From: brewmaster Date: Mon, 8 Jan 2024 17:58:58 +0900 Subject: [PATCH] fixed a typo (#337) Co-authored-by: Nicky Kim --- articles/intraprocess_communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/intraprocess_communication.md b/articles/intraprocess_communication.md index a2dedf13..56e0a467 100644 --- a/articles/intraprocess_communication.md +++ b/articles/intraprocess_communication.md @@ -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.