Merged
Conversation
Adding three new targeting criteria to facilitate Adaptive Performance. Distinct from the existing memory tier options, these use different thresholds based on 2025 data and exact cutoffs of 16384 and 8192), based on assessment of "gray areas" near the 8GB and 16GB thresholds, where a collective 40% risks being allocated to a higher tier. For Adaptive Performance, we want to intentionally err to the side of conservatism when applying optimizations on a user's behalf. User feedback also indicates a primary concern around battery life and resource usage, which is incidentally targeted by biasing away from more aggressive resource allocation that we intend for "true" high end devices or "power users".
tyler-thorne
requested review from
freshstrangemusic,
jaredlockhart and
yashikakhurana
as code owners
jaredlockhart
approved these changes
Dec 18, 2025
Collaborator
jaredlockhart
left a comment
jaredlockhart
left a comment
There was a problem hiding this comment.
Looks good thanks @tyler-thorne !
Contributor
Author
Thank you, @jaredlockhart ! |
Formatting line length
formatting
formatting
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We need new targeting criteria for Adaptive Performance, which will tune preferences based on device and session characteristics. This PR unlocks our immediate phase of experimentation around static device tiers.
Distinct from the two existing memory tier constants, these three use strategic thresholds informed by 2025 data and exact cutoffs of 16384 and 8192 (rather than 16000 and 8000), based on assessment of "gray areas" at 8GB and 16GB thresholds, where a collective 40% of devices may be allocated to higher tiers (analysis linked below). For Adaptive Performance, we want to intentionally err to the side of conservatism when applying optimizations on behalf of our users. User feedback also indicates a primary concern around resource usage and battery consumption, which is incidentally supported by biasing away from more aggressive resource allocation that we intend for "true" high end devices or "power users".
Side note, in relation to feedback received in experimenter office hours 16 Dec 2025: given that these thresholds may change after initial rounds of experimentation and feedback from engineering, we have not yet parameterized with code snippets.
Gray Zone Analysis: bquxjob_6c46232d_19b24ca47d0.csv