-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit threads per zenoh session #95
Conversation
Signed-off-by: Yadunund <yadunund@openrobotics.org>
cb682f8
to
6a7a918
Compare
The Zenoh configuration looks good to me. For tracking purposing, I link here a forthcoming PR on Zenoh (eclipse-zenoh/zenoh#566) which will impact the configuration of the Zenoh runtime. Note the the PR will impact only the configuration file, not CMake. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides what I said inline, do we need a similar configuration for the router build/config file? I don't know the answer, so just asking here.
// Number of threads dedicated to transmission | ||
// By default, the number of threads is calculated as follows: 1 + ((#cores - 1) / 4) | ||
threads: 1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the CMakeLists.txt, we have a nice comment explaining why we want to limit the threads. Can we have a similar comment here? It might also be a good idea to link to the PR that Luca mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Yadunund <yadunund@openrobotics.org>
Fix #94 by passing
"--no-default-features;--features=zenoh/transport_tcp"
to the cargo command invoked when buildingzenoh-c
. The default session config is also updated to limit the threads to 1.Special thanks to @cottsay for advising on how to deal with the
;
s in cmakecc: @Mallets