Skip to content

SortPeers()'s current pinging strategy may not scale #5

Description

@t-lin

SortPeers() currently sorts using results from on-the-spot sequential pinging of peers. This approach will not scale as the number of peers grow, and it only provides instantaneous RTT results (disregarding historical performance).

Possible solutions include:

  • Using some type of cache structure like pcache in the service-manager repo
    • Leave the pinging to be done by some other thread/goroutine (i.e. only ping allocators, and only allocators within some distance or with some metadata tag indicating region?)
  • Somehow leveraging Prometheus information
    • Need to figure out how to populate it with peer-to-peer latency info, which may not be totally scalable, as that means the database will nee to include full-mesh info

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions