Tranquil IT Forum

Hello,

I have two VMs on the same physical server running Windows Server 2019 (console and server) (a full SSD M.2 12-core, 32GB server). I have
a 10GB card
(Rev 2.3.0.113516)
There are two remote repositories

a large, simultaneous deployment for a school, so the Adobe suite can be deployed all at once for a class of 35 workstations.

When we launch this type of deployment, the console becomes unresponsive or even crashes completely.

Sometimes, at startup, the console fails to connect with a "no reachable server" message.

Have you encountered this issue before? Is WAPT designed for very large packages, 5 or even 10GB?
We followed the server optimization procedure in your documentation, but I didn't get the impression that it made any difference.

Hello,

is the WAPT server on the same LAN as the management machine and the client workstations? Or is it in a data center with a VPN connection between the two? Have you checked what's loading the machine (CPU, RAM, I/O)? We have clients that distribute large packets without major issues, especially for a small deployment of 35 workstations... Configuring it in uwsgi mode can also help on the server side for certain types of load, but I don't think that's the problem in your case.

Regards,

Denis

Hello,

what's strange is that the server and console aren't overloaded.
Both virtual machines are on the same LAN.

After launching several deployments with large packages, the console goes into unresponsive mode for the duration of the deployments, and we can no longer navigate it.

In the evening, when the students have left and half the computers are turned off, everything is fine.

Could this be due to the number of agent requests on the server?

Hello everyone,

following debugging with Geoffroy, it seems that the nginx.exe server on Windows quickly becomes saturated when downloading large volumes (package size * number of machines). In this case, the download was saturating at 800 Mbps and slowing down the console, which, with dozens of machines and 10-15 GB packages, was also slowing down nginx.

Switching the WAPT server to Linux resolved the issue; the console is now responsive and downloads are much faster.

As mentioned in the documentation, it is recommended to install the WAPT server on Linux, primarily due to the limitations of nginx on Windows. Therefore, if the WAPT server on Windows starts to slow down, it is recommended to switch it to Linux. For this, you can refer to the WAPT server backup and restore documentation.

I am marking the topic as SOLVED and locking it.

Best regards,

Denis.