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

APT-6135: Python point_cloud2.read_points significantly optimized by avoiding per-byte reading #18

Merged

Conversation

iurii-provizio
Copy link
Contributor

No description provided.

Copy link

@kevmcapro kevmcapro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated provizio_dds with python3 -m pip install -v git+https://github.com/provizio/provizio_dds.git@feature/APT-6135-point_cloud2.read_points-Optimization to test the optimisation.

For odometry, before optimisation read_points took 23% of processing time and 1.57% after optimisation. For freespace, before optimisation read_points took 31.92% of processing time and 1.81% after optimisation.

The next biggest bottleneck for freespace is the map_coordinates function and one of the for loops in pointc_registration for odometry.

@iurii-provizio iurii-provizio merged commit fd02a6b into develop Nov 18, 2024
@iurii-provizio iurii-provizio deleted the feature/APT-6135-point_cloud2.read_points-Optimization branch November 18, 2024 15:58
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

Successfully merging this pull request may close these issues.

2 participants