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
The main conclusion is that using babeltrace2 via their python API (https://babeltrace.org/docs/v2.0/python/bt2/) results in an ingestion that takes ~70s versus ~42s for the original babeltrace API. This was processing 865k events with kernel and user space events.
Investigate using
babeltrace2
for ingesting trace files from disk: https://github.com/efficios/babeltrace(Issue moved from GitLab, see: https://gitlab.com/ros-tracing/ros2_tracing/-/issues/45)
The text was updated successfully, but these errors were encountered: