Skip to content

Conversation

@gzliudan
Copy link
Collaborator

Proposed changes

Ref: ethereum#21263

Types of changes

What types of changes does your code introduce to XDC network?
Put an in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)
  • Regular KTLO or any of the maintaince work. e.g code style
  • CICD Improvement

Impacted Components

Which part of the codebase this PR will touch base on,

Put an in the boxes that apply

  • Consensus
  • Account
  • Network
  • Geth
  • Smart Contract
  • External components
  • Not sure (Please specify below)

Checklist

Put an in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

  • This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
  • Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
  • Tested the backwards compatibility.
  • Tested with XDC nodes running this version co-exist with those running the previous version.
  • Relevant documentation has been updated as part of this PR
  • N/A

@gzliudan gzliudan changed the title eth/downloader: refactor downloader + queue #21263 [WIP] eth/downloader: refactor downloader and queue #21263 May 20, 2025
@gzliudan gzliudan force-pushed the refactor-downloader branch 2 times, most recently from 884b118 to 5f0bb4b Compare May 21, 2025 05:56
@gzliudan gzliudan changed the title [WIP] eth/downloader: refactor downloader and queue #21263 eth/downloader: refactor downloader and queue #21263 May 21, 2025
@gzliudan gzliudan changed the title eth/downloader: refactor downloader and queue #21263 [WIP] eth/downloader: refactor downloader and queue #21263 May 22, 2025
@gzliudan gzliudan force-pushed the refactor-downloader branch from 5f0bb4b to fdc5ff2 Compare May 26, 2025 07:35
@gzliudan gzliudan changed the title [WIP] eth/downloader: refactor downloader and queue #21263 eth/downloader: refactor downloader and queue #21263 May 26, 2025
@gzliudan gzliudan force-pushed the refactor-downloader branch from fdc5ff2 to 2264c27 Compare June 3, 2025 04:32
* eth/downloader: refactor downloader + queue

downloader, fetcher: throttle-metrics, fetcher filter improvements, standalone resultcache

downloader: more accurate deliverytime calculation, less mem overhead in state requests

downloader/queue: increase underlying buffer of results, new throttle mechanism

eth/downloader: updates to tests

eth/downloader: fix up some review concerns

eth/downloader/queue: minor fixes

eth/downloader: minor fixes after review call

eth/downloader: testcases for queue.go

eth/downloader: minor change, don't set progress unless progress...

eth/downloader: fix flaw which prevented useless peers from being dropped

eth/downloader: try to fix tests

eth/downloader: verify non-deliveries against advertised remote head

eth/downloader: fix flaw with checking closed-status causing hang

eth/downloader: hashing avoidance

eth/downloader: review concerns + simplify resultcache and queue

eth/downloader: add back some locks, address review concerns

downloader/queue: fix remaining lock flaw

* eth/downloader: nitpick fixes

* eth/downloader: remove the *2*3/4 throttling threshold dance

* eth/downloader: print correct throttle threshold in stats

Co-authored-by: Péter Szilágyi <[email protected]>
@gzliudan gzliudan force-pushed the refactor-downloader branch from 2264c27 to 4dbd771 Compare June 9, 2025 06:01
@gzliudan gzliudan merged commit e8c9fdd into XinFinOrg:dev-upgrade Jun 17, 2025
13 checks passed
@gzliudan gzliudan deleted the refactor-downloader branch June 17, 2025 05:01
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.

3 participants