graft-project / GraftNetwork

Graft Network Proof-of-work Node

https://graft.network

Other

82 stars 41 forks source link

Excessive bandwidth usage since 1.9.2 #347

Open waterfallm opened 5 years ago

waterfallm commented 5 years ago

I've updated graftnetwork to 1.9.2 and over the last 10 days i've used almost 2.5 Tb bandwidth.

No unwanted processes and top network consumer is GraftNetwork/graftnoded

Anyone else seeing similar issues?

Ubuntu 18.04 with latest patches applied.

waterfallm commented 5 years ago

Annotation 2019-10-15 193318

waterfallm commented 5 years ago

graftnoded consantly > 2Mb/Sec sent

poolbomb commented 5 years ago

@waterfallm - there is no point is posting mate. Development has been abandoned. No one will care, no one will answer, because there are no devs left who can actually answer your question. Slava has zero clue about the current architecture, and I doubt he even knows any C++ - hell, I doubt he even know how to set up a SN by himself. So ... sorry to say, you're wasting your time here

waterfallm commented 5 years ago

thats tells me what i need to know. I'll just shut the server down before the bandwidth runs out

BKdilse commented 3 years ago

still an issue with v1.10.0.

avastar commented 3 years ago

For now, you could cap your outbound bandwidth. Most likely it is other nodes downloading the blockchain.

On Tue, Aug 31, 2021 at 2:18 PM BK @.***> wrote:

still an issue with v1.10.0.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/graft-project/GraftNetwork/issues/347#issuecomment-909600211, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKSHIISNH63LYSEYGJFI6DT7U2JDANCNFSM4JBAJCLQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

BKdilse commented 3 years ago

Yeah, that's what I ended up doing. I did have a look at the limits changes in the code, but I couldn't pinpoint where the issue was.

Stardock2018 commented 3 years ago

bandwidth settings

out-peers=32 # This will enable much faster sync and tx awareness; the default 8 is suboptimal nowadays in-peers=32 # The default is unlimited; we prefer to put a cap on this limit-rate-up=1048576 # 1048576 kB/s == 1GB/s; a raise from default 2048 kB/s; contribute more to p2p network limit-rate-down=1048576 # 1048576 kB/s == 1GB/s; a raise from default 8192 kB/s; allow for faster initial sync