Performance degression on Kovan

[5chdn]

• Parity Ethereum version: 2.3.0
• Operating system: Linux
• Installation: auto-updater
• Fully synchronized: yes
• Network: kovan
• Restarted: yes

 > tac parity-error-1.log | grep Starting
2019-01-16 01:08 +00:00: 2019-01-16 01:08:51 UTC Starting Parity-Ethereum/v2.3.0-beta-10657d9-20190115/x86_64-linux-gnu/rustc1.31.1
2018-12-25 19:11 +00:00: 2018-12-25 19:11:07 UTC Starting Parity-Ethereum/v2.2.5-beta-7fbcdfe-20181213/x86_64-linux-gnu/rustc1.31.0

After upgrading from 2.2.5 to 2.3.0 on Kovan, the following happened:

[ddorgan]

There's also a large increase in bandwidth usage, Terabytes of traffic...:

[ddorgan]

@5chdn did you not see this on your QA systems?

[5chdn]

I was fairly busy this week. Good thing @fevo1971 spotted this

[TriplEight]

that would be unbelievable if the discovery system is the cause.

[ddorgan]

It's pretty strange because the main net bootnodes don't seem to have the same issue....

[jam10o-new]

Since this appears to be appearing from 2.2.7 and 2.3.0 it is almost certainly caused by #10167 - if a node is on a more sparse network (testnets/private nets), the bandwidth usage seems to be much higher - due to discovery pings maybe?

[teodor-pripoae]

Hi, I'm having the same issue on kovan network. I've upgraded on 17 January from v2.1.6 to v2.2.7. Traffic increased to terrabytes, it costs hundreds of dollars in the cloud.

On mainnet running the same version it uses max 500kb/s.

On kovan:

On mainnet:

[teodor-pripoae]

Downgrading to 2.2.6 solved the problem so I think the regression was introduced in 2.2.7.

[petehall73]

Hi @5chdn, I see you removed the P2 tag on this bug. I'm not sure that's correct. I understand that this is as a result of the security patch but the massive increase in traffic is a huge problem for anyone hosting a node in the cloud and is billed for outbound network traffic. I'm managing the situation by restricting peers and pending peers but that's merely a workaround. I'd like to see this given a higher priority as it would force me to seek alternatives.

[ddorgan]

@petehall73 somebody is working on fix on this, an update will be posted here once it's ready and tested.