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

feat: Add HashStringAllocator::InputStream #12364

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Yuhta
Copy link
Contributor

@Yuhta Yuhta commented Feb 17, 2025

Summary:
When we get ByteInputStream from HashStringAllocator, we used to
have to materialize all the byte ranges in a vector, which is not efficient.
This change improve the efficiency by creating a ByteInputStream directly over
the linked list of a multi-part allocation.

Differential Revision: D69750088

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Feb 17, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D69750088

Copy link

netlify bot commented Feb 17, 2025

Deploy Preview for meta-velox canceled.

Name Link
🔨 Latest commit d8f1814
🔍 Latest deploy log https://app.netlify.com/sites/meta-velox/deploys/67b4a203ef80ad0008323434

… map (facebookincubator#12362)

Summary:

1. Optimize `deserializeString` in case of inlined strings
2. Optimize `deserializeArray` to avoid heap allocation for intermediate null-like data
3. Inline `FlatVector<StringView>::setNoCopy`

Differential Revision: D69750091
Summary:

In some cases (e.g. row-wise deserialization) we need to resize the
string vector frequently.  In that case none of the ASCII info is valid, but we
still pay the price to lock and check the state.  Fix the cost by using an
atomic boolean for fast path check.

Differential Revision: D69750090
Summary:

When we get `ByteInputStream` from `HashStringAllocator`, we used to
have to materialize all the byte ranges in a vector, which is not efficient.
This change improves the efficiency by creating a `ByteInputStream` directly over
the linked list of a multi-part allocation.

Differential Revision: D69750088
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D69750088

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants