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

benchmark tool reports higher than 100% recorded percentage #642

Closed
y-okumura-isp opened this issue Feb 9, 2021 · 2 comments
Closed

benchmark tool reports higher than 100% recorded percentage #642

y-okumura-isp opened this issue Feb 9, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@y-okumura-isp
Copy link

Description

rosbag2_performance_benchmarking reports higher than 100% recorded percentage.

Expected Behavior

<= 100%

Actual Behavior

When we run test with transport mode, we got the following report.

        Recorded messages for different caches and storage config:
                storage config: default:
                        cache [bytes]: 100,000,000: 100.04% recorded

To Reproduce

Change no_transport: False.
https://github.com/ros2/rosbag2/blob/master/rosbag2_performance/rosbag2_performance_benchmarking/config/benchmarks/test.yaml#L8

And follow the steps in https://github.com/ros2/rosbag2/tree/master/rosbag2_performance/rosbag2_performance_benchmarking.

$ ros2 launch rosbag2_performance_benchmarking benchmark_launch.py benchmark:=`ros2 pkg prefix rosbag2_performance_benchmarking`/share/rosbag2_performance_benchmarking/config/benchmarks/test.yaml producers:=`ros2 pkg prefix rosbag2_performance_benchmarking`/share/rosbag2_performance_benchmarking/config/producers/mixed_110Mbs.yaml

$ scripts/report_gen.py -i <BENCHMARK_RESULT_DIR>

System (please complete the following information)

  • OS: ubuntu 20.04
  • ROS 2 Distro: rolling
  • Version: 7548a04

Additional context

  • report_gen.py looks total_recorded_count in results.csv
  • total_recorded_count is from message_count in metadata.yaml
  • message_count contains ALL topics including /rosout or /parameter_events and so on.

It looks OK to filter message counts in result_utils.cpp.

@y-okumura-isp y-okumura-isp added the bug Something isn't working label Feb 9, 2021
y-okumura-isp added a commit to y-okumura-isp/rosbag2 that referenced this issue Feb 9, 2021
Signed-off-by: y-okumura-isp <y-okumura@isp.co.jp>
@adamdbrw
Copy link
Collaborator

The reason is catching /rosout. Currently two ways to fix it:
#634 employs filtering by regex to only count topics from benchmarking tool
#643 extends parsing of metadata yaml file to only count with a given namespace

@y-okumura-isp
Copy link
Author

As I closed PR #643, I also close this issues.

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

Successfully merging a pull request may close this issue.

2 participants