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

[Performance issues] Unstable CPU usage, 19%-41.6% #16

Open
zymouse opened this issue Mar 12, 2024 · 2 comments
Open

[Performance issues] Unstable CPU usage, 19%-41.6% #16

zymouse opened this issue Mar 12, 2024 · 2 comments

Comments

@zymouse
Copy link

zymouse commented Mar 12, 2024

Introducing.

ros2_v4l2_camera is a great hardware accelerated camera ros driver. I did the following test.

test environment

  • jetpack6.0
  • Jetson AGX Orin
  • ros2 humble
  • branch: galactic
  • commit:1029edd3a763b73ac44aad0c5175f1ef88c42d4d
  • ros2 run rqt_image_view rqt_image_view
    image

Determined in advance:

  • It works fine, I can subscribe to the "Camera Images" thread properly!
  • Using the same camera: sensing

Problem Description:
The test environment is the same as the test method

  • Starting ros2 run v4l2_camera v4l2_camera_node
  • Using ros2 run rqt_image_view rqt_image_view

Test Description:
CPU usage stabilized at around 20% in the morning test
image

In the afternoon, the CPU usage stabilized at around 37%.
image

The CPU usage is not the same in both tests, which I don't think is a normal phenomenon

@knzo25

@zymouse zymouse changed the title [Performance issues] Unstable CPU usage, 19%-38.3% [Performance issues] Unstable CPU usage, 19%-41.6% Mar 12, 2024
@knzo25
Copy link

knzo25 commented Mar 12, 2024

@manato
I think this falls under your expertise rather than mine 😅

@manato
Copy link
Collaborator

manato commented Apr 26, 2024

@knzo25
Thanks for connecting.

@zymouse
The CPU usage possibly gets higher just after trying to establish ROS connection, and then gets stable at low usage after a while. I would appreciate it if you check the usage after a while to see the usage gets stable. Besides, I guess the reported value might vary depending on the load sample frequency. When you observe a similar high CPU usage, I would also appreciate if you could restart load measurements a few times just in case. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants