You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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++
The text was updated successfully, but these errors were encountered:
Please provide the following information:
Expected behaviour
Diagnostics take 1-2% CPU, not 22% steady state
Actual behaviour
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++
The text was updated successfully, but these errors were encountered: