We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
rospy create multiple threads in a few places...
This means there is one thread per topic (publisher side for async send) it seems.
These threads being OS threads, there will be fighting for CPU resources in OS scheduler (with context switching overhead).
It would be nice to propose alternatives to the user...
Maybe pyros could duck punch the threading module for rospy and allow using greenthreads ?
or maybe a patch directly in rospy ?
The text was updated successfully, but these errors were encountered:
Greenthread might be a small improvement. but ultimately we should consider an async framework : https://www.youtube.com/watch?v=82vuCZ4FLFE
Sorry, something went wrong.
No branches or pull requests
rospy create multiple threads in a few places...
This means there is one thread per topic (publisher side for async send) it seems.
These threads being OS threads, there will be fighting for CPU resources in OS scheduler (with context switching overhead).
It would be nice to propose alternatives to the user...
Maybe pyros could duck punch the threading module for rospy and allow using greenthreads ?
or maybe a patch directly in rospy ?
The text was updated successfully, but these errors were encountered: