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

Investigate removing nullmask from parse_uri results when not needed #1727

Open
hyperbolic2346 opened this issue Jan 24, 2024 · 0 comments
Open

Comments

@hyperbolic2346
Copy link
Collaborator

As brought up in review, the nullmask is potentially unnecessary. If the input doesn't have a nullmask the result could still need one. This doesn't mean that it will though as the input URI's could all be valid results.

This investigation is to weigh the performance impact vs the memory savings of removing the nullmask when it is possible. This could require marching the mask afterward or having an atomic the kernel updates based on nulls.

Originally posted by @nvdbaranec in #1704 (comment)

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

No branches or pull requests

1 participant