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

Possible Speed Ups #2

Open
william-silversmith opened this issue Feb 3, 2024 · 0 comments
Open

Possible Speed Ups #2

william-silversmith opened this issue Feb 3, 2024 · 0 comments
Labels
performance Make it faster or lower memory.

Comments

@william-silversmith
Copy link
Contributor

william-silversmith commented Feb 3, 2024

The code is much faster than it was at the start. An est. 25 core-years is now reduced to 30 minutes for a dense run on connectomics.npy.ckl. However, this is still much longer than it takes to process skeletons with Kimimaro!

One possibility for moving faster is instead of processing single voxels at a time, work with larger and larger cubes and compute the area that way. However, it will take some effort to efficiently distinguish between area that are "safe" and areas that requires more precision.

One other possibility is to determine a bounding box, compute the area for that box, and work on the outside and subtract area from the result. If the box is tight and there are no holes in the interior, then this could be efficient... but it only works if you know there's a single connected component.

@william-silversmith william-silversmith added the performance Make it faster or lower memory. label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Make it faster or lower memory.
Projects
None yet
Development

No branches or pull requests

1 participant