[Draft] Merging the upstream/rolling EventsExecutor here #141
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.
Getting this started. This PR pulls in the EventsExecutor code from the upstream
rclcpp
,rolling
branch into here.Locally:
irobot_lock_free_events_queue
(which remains where it is...)With respect to the ros2-performance framework, on an iRobot robot, I ran 60-sec
white_mountain
multiple times with each EventsExecutor:EventsExecutor from the dedicated iRobot repo, CPU-utilization, last line
"upstream" EventsExecutor, from the experimental namespace, CPU-utilization, last line