Skip to content

Double check other client limits #8475

Open
@asdacap

Description

@asdacap
  • Perf/More accurate request limit. #8474 allow sync code to know what should be the request limit per peer.
  • For bodies, receipts and headers, the limit can be different depending on client type.
  • This is specified in Nethermind.Synchronization.SyncLimits.*SyncLimits and it is likely outdated.

Task

  • Double check other client header, bodies, receipts and snap limits.
  • Update the values.
  • Move Nethermind.Synchronization.SyncLimits.*SyncLimits to Nethermind.Stats.
  • Double check the returned value in NodeStatsLight.GetCurrentRequestLimit is correct.
  • Optionally, limit node request in TreeSync, and double check if there are other limit to be added in snapsync.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions