-
Notifications
You must be signed in to change notification settings - Fork 892
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
Firestore: Choose DEFAULT_RELATIVE_INDEX_READ_COST_PER_DOCUMENT value based on the browser, rather than hardcoding 8 #7929
Merged
dconeybe
merged 2 commits into
master
from
dconeybe/RelativeIndexReadCostFromExperimentRatherThanHardcoding8
Jan 8, 2024
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
…ER_DOCUMENT based on the browser, rather than hardcoding 8
🦋 Changeset detectedLatest commit: b5424e3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
dconeybe
changed the title
Firestore: query_engine.ts: choose DEFAULT_RELATIVE_INDEX_READ_COST_PER_DOCUMENT based on the browser, rather than hardcoding 8
Firestore: Choose DEFAULT_RELATIVE_INDEX_READ_COST_PER_DOCUMENT value based on the browser, rather than hardcoding 8
Jan 8, 2024
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1This report is too large (482,330 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
cherylEnkidu
approved these changes
Jan 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you !
dconeybe
deleted the
dconeybe/RelativeIndexReadCostFromExperimentRatherThanHardcoding8
branch
January 8, 2024 22:22
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A previous PR, #7608, hardcoded the value of
DEFAULT_RELATIVE_INDEX_READ_COST_PER_DOCUMENT
to 8. At the time, this was the "worst case" value, but penalized many platform/browser combinations that would experience performance benefits from a lower value.Since then, an experiment was performed to calculate a more reasonable value. These optimal values were:
This PR changes the hardcoded value of 8 to one of the values above, depending on the runtime environment.
NOTE: This PR accidentally increased the code bundle size by 6.5 kB starting in v10.7.2. This bundle size regression was fixed by #8178.