Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Massive bandwidth consumption on kovan network #10403

Closed
ddorgan opened this issue Feb 22, 2019 · 6 comments
Closed

Massive bandwidth consumption on kovan network #10403

ddorgan opened this issue Feb 22, 2019 · 6 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone

Comments

@ddorgan
Copy link
Collaborator

ddorgan commented Feb 22, 2019

Parity Ethereum version: stable / beta

  • Operating system: linux
  • Installation: one-line installer
  • Fully synchronized: yes
  • Network: Kovan
  • Restarted: yes

There was a very large increase of traffic since 2.2.7 and 2.3.0

image

@jam10o-new jam10o-new added F2-bug 🐞 The client fails to follow expected behavior. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. M4-core ⛓ Core client code / Rust. labels Feb 24, 2019
@jam10o-new jam10o-new added this to the 2.5 milestone Feb 24, 2019
@gabreal
Copy link
Contributor

gabreal commented Mar 1, 2019

follow up issue of #10230

@jam10o-new jam10o-new added P0-dropeverything 🌋 Everyone should address the issue now. and removed P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Mar 8, 2019
@teodor-pripoae
Copy link

Any new info regarding this issue ? I'm running 2.3.5 and have the same issue.

Screenshot 2019-03-11 15 18 57

Screenshot 2019-03-11 15 19 01

@ordian
Copy link
Collaborator

ordian commented Mar 13, 2019

@teodor-pripoae I've tried both 2.2.6 and 2.2.5 with "Constantinople fix" applied (#10214 and #10223, see ao-kovan-experiments branch) (otherwise it won't sync) and it seems like they produce/consume about the same amount of traffic per connected peer:
2 2 5
(the first spike is deploying 2.2.6 and the second is 2.2.5)

Are you sure it is not merely caused by more peer connections? Can't find any evidence it isn't.

@teodor-pripoae
Copy link

Hi @ordian . I did not change anything in my configuration since upgrading from 2.x to 2.2.10 and then to 2.3.5 and it currently consumes about 3mb/s traffic.

I will try building a docker image from your branch.

@jam10o-new jam10o-new added P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. and removed P0-dropeverything 🌋 Everyone should address the issue now. labels Mar 27, 2019
@soc1c soc1c modified the milestones: 2.5, 2.6 Apr 2, 2019
@soc1c
Copy link
Contributor

soc1c commented Apr 2, 2019

Is this resolved?

@ddorgan
Copy link
Collaborator Author

ddorgan commented Apr 2, 2019

@soc1c looks like it's resolved....

image

@soc1c soc1c closed this as completed Apr 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. M4-core ⛓ Core client code / Rust. P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Projects
None yet
Development

No branches or pull requests

6 participants