[#1364] Increase BLOCKS_METADATA_BUFFER_SIZE

[HonzaR]

• Closes Increase BLOCKS_METADATA_BUFFER_SIZE to match (or be closer to) download batch size #1364
• Filed another related improvement issue Keep BLOCKS_METADATA_BUFFER_SIZE the same as current SYNC_BATCH_SIZE #1555
• The implemented changes still work well for the sandblasting period, too, where we sync batch of 100 blocks.
• Changelog update

Block synchronization tests results:

Restore older wallet (122K blocks):
Before:
10:04:18.586 - 09:39:49.527 = 00:24:29
After:
10:20:13.480 - 10:07:22.831 = 00:12:50
= cca -48.5%

New wallet: (2.5K blocks):
Before:
10:41:23.064 - 10:40:47.286 = 00:00:35.778
After:
10:44:26.194 - 10:44:07.951 = 00:00:18.000000
= cca -50%

Note
This code review checklist is intended to serve as a starting point for the author and reviewer, although it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation). For more in-depth discussion of how we think about code review, please see Code Review Guidelines.

Author

• Self-review your own code in GitHub's web interface¹
• Add automated tests as appropriate
• Update the manual tests² as appropriate
• Check the code coverage³ report for the automated tests
• Update documentation as appropriate (e.g README.md, Architecture.md, etc.)
• Run the demo app and try the changes
• Pull in the latest changes from the main branch and squash your commits before assigning a reviewer⁴

Reviewer

• Check the code with the Code Review Guidelines checklist
• Perform an ad hoc review⁵
• Review the automated tests
• Review the manual tests
• Review the documentation, README.md, Architecture.md, etc. as appropriate
• Run the demo app and try the changes⁶

Footnotes

1. Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs. ↩

2. While we aim for automated testing of the SDK, some aspects require manual testing. If you had to manually test
   something during development of this pull request, write those steps down. ↩

3. While we are not looking for perfect coverage, the tool can point out potential cases that have been missed. Code coverage can be generated with: ./gradlew check for Kotlin modules and ./gradlew connectedCheck -PIS_ANDROID_INSTRUMENTATION_TEST_COVERAGE_ENABLED=true for Android modules. ↩

4. Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit. ↩

5. In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass. ↩

6. While the CI server runs the demo app to look for build failures or crashes, humans running the demo app are
   more likely to notice unexpected log messages, UI inconsistencies, or bad output data. Perform this step last, after verifying the code changes are safe to run locally. ↩

[str4d]

utACK 6ad1021

[HonzaR]

I just did one more manual test now on the Pixel 8 Pro emulator for a wallet that covers the sandblasting period:

It's Alice's wallet from the SDK fixture values.

• The after state contains both:
  • SYNC_BATCH=1000 (or 100 in sandblasting)
  • BLOCKS_METADATA_BUFFER_SIZE=1000 for the whole range.
• The before state:
  • It does not include any of the above-mentioned improvement

2603531 - 1935001 = 668,530 (i.e. cca 115K blocks in the sandblasting period)
———
Before:
10:47:10.276 - 08:55:40.430 = 01:51:29
After:
10:16:18.025 - 08:55:55.730 = 01:20:22

The result is about 27.90% faster now. I read this as the significant improvement coming mostly out of the sandblasting period, which is expected.