Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Decrease Neighbor Stats Compression Latency #49

Open
vuapo-eth opened this issue Mar 7, 2019 · 0 comments
Open

Decrease Neighbor Stats Compression Latency #49

vuapo-eth opened this issue Mar 7, 2019 · 0 comments
Labels
api Extra attention is needed bug Something isn't working

Comments

@vuapo-eth
Copy link
Contributor

#31 already addressed the stats history submitted by the API growing too large. The issue was fixed with 13b237a which compresses the internally available stats history before submitting through the API. The way this is currently done does not scale well though resulting in an increasing timeout and node load when requesting neighbor stats (at least not causing issues in the GUI as before).

By introducing at least one of the following strategies, this timeout latency could be reduced significantly:

  • statistical compression: consider only a subset of the history acting as sample for the entire history (e.g. only consider every 5th round and multiply the stats of that round by 5)
  • stateful compression: introduce a state so that previously calculated compressions can be reused
@vuapo-eth vuapo-eth added bug Something isn't working api Extra attention is needed labels Mar 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api Extra attention is needed bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant