Skip to content

Conversation

@cthulhu-rider
Copy link
Contributor

No description provided.

@cthulhu-rider cthulhu-rider force-pushed the ec-shard-sort branch 2 times, most recently from 6eb5f75 to 7ed43b4 Compare January 13, 2026 14:12
@codecov
Copy link

codecov bot commented Jan 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 25.60%. Comparing base (d2624c8) to head (476652b).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3773   +/-   ##
=======================================
  Coverage   25.60%   25.60%           
=======================================
  Files         657      657           
  Lines       42102    42107    +5     
=======================================
+ Hits        10779    10781    +2     
- Misses      30344    30347    +3     
  Partials      979      979           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@cthulhu-rider cthulhu-rider marked this pull request as ready for review January 13, 2026 14:32
Previously, shards were sorted by parent address on writing and by part
address on reading. This generally led to suboptimal traversal of shards
on reading causing unavoidable misses. To prevent this, selection
algorithms must be synchronized.

This makes `StorageEngine.Put()` to sort shards by parent ID when EC
part is being written.

Closes #3537.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
@roman-khimov roman-khimov merged commit ac58838 into master Jan 15, 2026
22 checks passed
@roman-khimov roman-khimov deleted the ec-shard-sort branch January 15, 2026 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants