Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3 GB of output traffic from Verus Desktop #176

Open
tkalfaoglu opened this issue Jan 20, 2023 · 2 comments
Open

3 GB of output traffic from Verus Desktop #176

tkalfaoglu opened this issue Jan 20, 2023 · 2 comments

Comments

@tkalfaoglu
Copy link

When I start the Verus Desktop app, only for maintaining my wallet, and no other functions, I observe over 3GB/sec of outgoing traffic.. Since I'm on VDSL2 with limited output bandwidth, it makes a big difference.
How can I limit the application's output?

@tkalfaoglu
Copy link
Author

I guess no one is alive here.

@michaeltout
Copy link

The calls that Verus Desktop makes are very dependant on what you're using it for, so providing more info would be the best way to get a concise answer.

Are you using primarily light mode or native mode? Do you have a large number of transactions? Where are the calls being made to?

I can imagine that in native mode the daemon subprocess might make quite a few calls while validating blockchain data and just syncing in general, while in lite mode bandwidth would increase if the data being processed was larger (e.g. large lists of transactions). There is no way at the moment to limit the applications output manually without knowing why you're observing 3GB/sec of traffic. For more help on this I would advise finding out more about your situation and maybe consulting the community discord at https://verus.io/discord, as this Github issues page is reserved more for reproducible and/or verifiable issues than general troubleshooting/questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants