Skip to content

serializer: Use match_byte in the serializer. #361

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

Merged
merged 1 commit into from
Sep 11, 2023
Merged

Conversation

emilio
Copy link
Member

@emilio emilio commented Sep 6, 2023

No description provided.

@emilio emilio requested a review from tiaanl September 6, 2023 14:14
@emilio emilio enabled auto-merge September 6, 2023 14:15
Copy link
Collaborator

@tiaanl tiaanl left a comment

Choose a reason for hiding this comment

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

+256 bytes of data per call site is unfortunate as the data is very sparse and mostly 0.

I wonder how the performance would be affected if you partition the lookup table. Say 16 bytes each, not creating blocks that are all 0, and then have a single u16 that has bits set for each "existing" block. If you hit a "non existent" block, you default out otherwise do the table lookup. No for this PR though 😄

@emilio emilio added this pull request to the merge queue Sep 11, 2023
Merged via the queue into master with commit c97ba60 Sep 11, 2023
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