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.

Sign up for GitHub

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

Jump to bottom

Optimize base16, base32 and base64 decoders #7

Closed
k0ekk0ek opened this issue Dec 20, 2022 · 2 comments
Closed

Optimize base16, base32 and base64 decoders #7

k0ekk0ek opened this issue Dec 20, 2022 · 2 comments
Labels
enhancement New feature or request
Milestone
Release 0.2.0

Comments

@k0ekk0ek
Copy link
Contributor

Base16, base32 and base64 decoding is currently done on a character-by-character base. Much research has been done to optimize decoding these types of formats using SIMD operations and since DNSSEC record types now make up much of the data in zone files, throughput should increase significantly.
@k0ekk0ek k0ekk0ek added the enhancement New feature or request label Dec 20, 2022
@k0ekk0ek k0ekk0ek added this to the Release 0.2.0 milestone Dec 20, 2022
@k0ekk0ek
Copy link
Contributor Author

k0ekk0ek commented Jan 13, 2023 •
edited
Loading

The flamegraph for parsing an .se zone looks nice and balanced, except for base64 data as the parser spends about 30% of the time in parse_base64.

@k0ekk0ek
Copy link
Contributor Author

Close in favor of #26, #27 and #28.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Release 0.2.0
Development

No branches or pull requests
1 participant
@k0ekk0ek