Theoretically calculate the maximum/worst case number of chunks Used

[deepaksree]

Brief feature description

Is there a way to theoretically calculate the maximum and worst case number of chunks that will be used in runtime. I have a single publisher and multiple subscriber system.

Detailed information

A mathematical formula or description to calculate the worst case chunk usage in single publisher multiple subscriber system.

[elfenpiff]

@deepaksree You can do this effectively only with iceoryx2. Due to the central broker and the central configuration the worst case number of chunks would be extremely huge.

This is one of the many reasons why we created iceoryx2.

[elBoberido]

While calculating is not so easy, you could use the introspection client to get an overview of the chunks in use.

Calculating depends on the configured queue sizes and how many chunks a subscriber and publisher can hold in parallel and also the history size. This can become quite large for a whole system.

In theory it should be something like MAX_CHUNKS_ALLOCATED_PER_PUBLISHER_SIMULTANEOUSLY + MAX_PUBLISHER_HISTORY + MAX_CHUNKS_HELD_PER_SUBSCRIBER_SIMULTANEOUSLY * NUMBER_OF_SUBSCRIBER + QUEUE_SIZE_SUBSCRIBER_1 + QUEUE_SIZE_SUBSCRIBER_2 + ....

Does this answer your question? Can the issue be closed?