Skip to content
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

Clearpath diagnostics takes 20% of core on Jackal #63

Open
SteveMacenski opened this issue Jun 20, 2024 · 1 comment
Open

Clearpath diagnostics takes 20% of core on Jackal #63

SteveMacenski opened this issue Jun 20, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@SteveMacenski
Copy link

Please provide the following information:

  • OS: 22.04
  • ROS 2 Distro: Humble
  • Built from source or installed: Jackal hardware
  • Real hardware or simulation: real robot

Expected behaviour

Diagnostics take 1-2% CPU, not 22% steady state

Actual behaviour

image

Note that it takes almost double the CPU as running a 3D lidar driver publishing out 3D data at 10hz and half as much as the realsense doign 30fps on huge point clouds

This seems excessive for what it does. I suspect this can be massively reduced if implemented in C++

@SteveMacenski SteveMacenski added the bug Something isn't working label Jun 20, 2024
@tonybaltovski tonybaltovski self-assigned this Aug 14, 2024
@tonybaltovski
Copy link
Member

We are going to look at reworking in C++ for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants