CPU and Memory usage monitoring script for ROS #2467
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
engineering_tools/monitor-ros-cpu.py
Outdated
| python3 monitor-ros-cpu.py | ||
|
|
||
| 4. In a different terminal, start CARMA Platform: | ||
| ./carma start all |
There was a problem hiding this comment.
why do we have ../ for starting carma?
engineering_tools/monitor-ros-cpu.py
Outdated
|
|
||
|
|
||
| # Base path to save the CSV file | ||
| base_output_file = "cpu_usage_ros2_nodes.csv" |
There was a problem hiding this comment.
could you update the script so everything is saved in a folder? this way it would be easier to find/copy them after several runs.
engineering_tools/monitor-ros-cpu.py
Outdated
|
|
||
|
|
||
| # Function to create a unique filename by appending a number | ||
| def get_unique_filename(base_filename): |
There was a problem hiding this comment.
Could we follow the file naming convention of ROS bags and include the date/time? This would make it easier to correlate the script output with the ROS bag file.
|
saina-ramyar
approved these changes
Nov 18, 2024
This was referenced Nov 19, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Description
This PR supports efforts to create analysis scripts for control performance of CARMA. By running this before the carma starts, we are able to log the processes and see which one is taking more resources over time.
Example graph can be, which is not finalized and will be in the carma-analytics-fotda-repo.
Design document for this task is here: https://leidoscorpus.sharepoint.us/:w:/r/sites/STR/TODevelopmentLibrary/22-256%20CDA%20Design%20%26%20Architecture/Work-In-Progress/Task%207%20Architecture%20Improvement%20Implementation/CARMA%20Platform%20Controls%20Improvements/Identified%20Core%20Performance%20Metrics%20And%20Analysis%20Design%20for%20CARMA%20Platform%20Control.docx?d=w40615c2fbfb74d439215cf62c5e5c4ca&csf=1&web=1&e=NXYkMT
Before this, I tried looking to other methods, but this seemed most straightforward and without issue.
rqt_top is also deprecated in ROS2
ROS2_tracing kernel monitoring was really promising, but maybe it is due to foxy, we it was not possible to record the measurements.
Design task was done here and also mentions above other options I tried https://usdot-carma.atlassian.net/browse/ARC-207
Related GitHub Issue
NA
Related Jira Key
ARC-54
Motivation and Context
Control performance analysis script creation
How Has This Been Tested?
Tested on CDASim and on Live vehicle whether if it is gathering info fine.
Types of changes
Checklist: