Add Fixed PIR Shard Config #48
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
karulont
approved these changes
Nov 12, 2024
fboemer
force-pushed
the
fboemer/smaller-pir-config
branch
from
d0de3e5
to
d5f14be
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of iOS 18.2 (beta 2), when all shard configurations are identical,
PIR Fixed Shard Configallows for a more compact PIR config, saving bandwidth and client-side memory usage. To enable, set thepirShardConfigsfield in the PIR config. iOS clients prior to iOS 18.2 will still require theshardConfigsfield to be set. See Reusing PIR Parameters for how to process the database such that all shard configurations are identical.