DRAFT: [0.1.x patch] patch: further improve large read performance on Android with larger internal result chunk size - DO NOT MERGE#16
Draft
brody2consult wants to merge 2 commits into
Conversation
…Android with even larger internal result chunk size
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
1 participant
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.
backporting of update from PR #15 patch-0.1.x - SEE STATUS BELOW:
KNOWN TO CAUSE CRASH with large data test on Moto G9 Play when testing on Browser Stack
STATUS: I would still love to find a way to further increase the performance on 0.1.x, for benefit of Android 10 devices as discussed in #13. Maybe increase internal chunk cutoff size to 1 000 000 rather than 50 000 000, for example. I may revisit this if there is sufficient demand.