eclipse-iceoryx / eclipse-iceoryx/iceoryx

It is possible to specify a queue size greater than 256

Open
#2,317 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
2.2k
Forks
492
Avg merge
18h 57m
Merged PRs (30d)
1

Description

I do it like this

iox::popo::SubscriberOptions subscriberOptions;
subscriberOptions.queueCapacity = 5000U;
iox::runtime::PoshRuntime::initRuntime(name_app);
iox::popo::Listener listener;
iox::popo::UntypedSubscriber subscriber_ses({"SES", run_context, "Event"},subscriberOptions);

after

listener
    .attachEvent(subscriber_ses,
         iox::popo::SubscriberEvent::DATA_RECEIVED,
         iox::popo::createNotificationCallback(get_events_wrapper))
     .or_else([](auto) {
          ::fmt::print("Error\n");
});

I get this message
[Warning]: Requested queue capacity 5000 exceeds the maximum possible one for this subscriber, limiting from 5000 to 256

Sorry for the stupid question, but can I increase the queue?

I found it here https://iceoryx.io/latest/advanced/configuration-guide/

I tried to build it like this
cmake -Bbuild -Hiceoryx_meta -DBUILD_SHARED_LIBS=ON -DIOX_MAX_PUBLISHER_HISTORY=32768
but it didn't help

my publishers produce a lot of messages and I would like to get a little more than 256 at a time, can I do it somehow? I really need help :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with iox::popo::SubscriberOptions::queueCapacity, the UntypedSubscriber setup, and the warning that limits capacity to 256. Compare the configuration guide with the attempted I/OX_MAX_PUBLISHER_HISTORY CMake option to identify the relevant limit. Done means documenting or implementing a supported way to request a larger subscriber queue, with validation of the resulting capacity.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.