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

Such a tool needs a feature to limit bandwidth #110

Closed
myselfghost opened this issue Mar 7, 2023 · 6 comments
Closed

Such a tool needs a feature to limit bandwidth #110

myselfghost opened this issue Mar 7, 2023 · 6 comments
Labels
todo Something we need to do

Comments

@myselfghost
Copy link

In our experience of using similar tools, it may be necessary to limit the bandwidth of transmission in many cases.

@mstmdev
Copy link
Member

mstmdev commented Mar 7, 2023

Yes, that's good advice. We can try to limit the transmission rate in the server and client sides.

@mstmdev mstmdev added the todo Something we need to do label Mar 7, 2023
@mstmdev
Copy link
Member

mstmdev commented Mar 7, 2023

How about enabling compression in a low-rate environment to reduce transmission time?

@myselfghost
Copy link
Author

How about enabling compression in a low-rate environment to reduce transmission time?

The main purpose of throttling bandwidth is to avoid 100% bandwidth usage of the machine.

@mstmdev
Copy link
Member

mstmdev commented Mar 7, 2023

The main purpose of throttling bandwidth is to avoid 100% bandwidth usage of the machine.

Add a flag to control it, like -max_tran_rate=102400 (bytes/sec)?

@mstmdev
Copy link
Member

mstmdev commented Mar 10, 2023

WIP #111

@mstmdev
Copy link
Member

mstmdev commented Mar 12, 2023

#111 #112 have been merged, add the -max_tran_rate flag to support limit the max transmission rate in the server and client sides.

@mstmdev mstmdev closed this as completed Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
todo Something we need to do
Projects
None yet
Development

No branches or pull requests

2 participants