Bandwidth limitation and/or simultaneous customer limit
Published: March 8, 2021 - 4:40 PM
Hello,
Our organization decided to use WAPT about 8 months ago for practical reasons related to remote work.
Our server was installed and hosted at the company headquarters.
We had no problems initially, but with an increasing number of remote workstations, we are experiencing significant slowdowns at headquarters due to our total bandwidth consumption. We have approximately 800 workstations in total, 70-75% of which are remote, and a fiber optic connection limited to 20 Mbps. During an update of a medium-sized application, such as Firefox, our bandwidth is completely used, causing malfunctions elsewhere.
We are quite limited in our options and decisions, and our organization cannot implement QoS on its own; the choice of WAPT was ours.
We are currently seeking appropriate solutions to mitigate these issues without compromising the effectiveness of WAPT. Currently, external hosting is not an option, and we are unsure of its functionality due to our internal security measures.
We tested Wondershaper to limit bandwidth on an interface, but this solution is far too restrictive, both for us at headquarters using the console and for updating 800 simultaneous workstations with a cap of 8 Mbps and download speeds between 15 and 30 KB/s, whether they are remote or local workstations.
Is there, and do you know of, a solution that would allow us to limit the number of simultaneous updates, such as a queue (e.g., 10 workstations at the same time)?
On the server side, I see options in the documentation such as "db_max_connections" or "max_client" that we haven't tried yet, but I'm afraid that options like "max_client" might block some of our workstations until other workstations are disconnected first…
I also considered whether it would be possible, with two network interfaces, to limit the bandwidth of our remote users based on their IP address, and use the other interface for local IPs, but I don't see if such filtering is possible on the WAPT server side…
If you have any answers, we'd be very grateful!
Thank you!
WAPT Community 1.8.2
CentOS 7
Our organization decided to use WAPT about 8 months ago for practical reasons related to remote work.
Our server was installed and hosted at the company headquarters.
We had no problems initially, but with an increasing number of remote workstations, we are experiencing significant slowdowns at headquarters due to our total bandwidth consumption. We have approximately 800 workstations in total, 70-75% of which are remote, and a fiber optic connection limited to 20 Mbps. During an update of a medium-sized application, such as Firefox, our bandwidth is completely used, causing malfunctions elsewhere.
We are quite limited in our options and decisions, and our organization cannot implement QoS on its own; the choice of WAPT was ours.
We are currently seeking appropriate solutions to mitigate these issues without compromising the effectiveness of WAPT. Currently, external hosting is not an option, and we are unsure of its functionality due to our internal security measures.
We tested Wondershaper to limit bandwidth on an interface, but this solution is far too restrictive, both for us at headquarters using the console and for updating 800 simultaneous workstations with a cap of 8 Mbps and download speeds between 15 and 30 KB/s, whether they are remote or local workstations.
Is there, and do you know of, a solution that would allow us to limit the number of simultaneous updates, such as a queue (e.g., 10 workstations at the same time)?
On the server side, I see options in the documentation such as "db_max_connections" or "max_client" that we haven't tried yet, but I'm afraid that options like "max_client" might block some of our workstations until other workstations are disconnected first…
I also considered whether it would be possible, with two network interfaces, to limit the bandwidth of our remote users based on their IP address, and use the other interface for local IPs, but I don't see if such filtering is possible on the WAPT server side…
If you have any answers, we'd be very grateful!
Thank you!
WAPT Community 1.8.2
CentOS 7