Hello,
We currently have a Windows Server 2022 on which WAPT 2.6.1.17472 is installed and manages over 1000 agents (this installation has been in place for several years).
I have just consulted your documentation and noted that, when installed on a Windows server, WAPTServer can only support 200 agents due to a technical limitation related to Nginx.
At this stage, I haven't noticed any particular problems on our server. Can you confirm whether there is a risk in continuing with this configuration, or if it is recommended to migrate to a Linux server?
Thank you in advance for your reply.
Have a good day,
Christophe
[RESOLVED] Number of agents on Windows server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Christophe,
actually the problem with the 200-user limit isn't related to the Wapt code itself, but to Wapt's use of the Nginx web server. Nginx is a very good web server under Linux, but it hasn't been optimized for Windows at all. The Windows version doesn't support many "long" requests (several seconds) in parallel, such as during the installation of a large Wapt package or an OS deployment.
We therefore included this limitation in the documentation to allow support to direct the client to a Linux server if there are performance issues.
But if your server is working well for you, there's no rush to switch. That said, as a fan of command lines and black screens, I encourage you to look into Debian; once you've tried it, you won't want to go back.
Best regards,
Denis
actually the problem with the 200-user limit isn't related to the Wapt code itself, but to Wapt's use of the Nginx web server. Nginx is a very good web server under Linux, but it hasn't been optimized for Windows at all. The Windows version doesn't support many "long" requests (several seconds) in parallel, such as during the installation of a large Wapt package or an OS deployment.
We therefore included this limitation in the documentation to allow support to direct the client to a Linux server if there are performance issues.
But if your server is working well for you, there's no rush to switch. That said, as a fan of command lines and black screens, I encourage you to look into Debian; once you've tried it, you won't want to go back.
Best regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hi Christophe,
Well, it's my turn to respond to your post.
Yesterday, I started installing a 200MB update on about 100 machines simultaneously (I needed to see the result quickly), and my console froze for a good minute.
I don't know your server's specs, but mine has 4 vCPUs and 16GB of RAM, which must be limiting it a bit.
And since I've been using WAPT, this is the first time I think I've put this much strain on the server, because usually I let the machines manage their updates as they see fit.
I think the main thing is your own experience and, above all, properly sizing the server.
If I could, I'd definitely increase the RAM on mine...
Well, it's my turn to respond to your post.
Yesterday, I started installing a 200MB update on about 100 machines simultaneously (I needed to see the result quickly), and my console froze for a good minute.
I don't know your server's specs, but mine has 4 vCPUs and 16GB of RAM, which must be limiting it a bit.
And since I've been using WAPT, this is the first time I think I've put this much strain on the server, because usually I let the machines manage their updates as they see fit.
I think the main thing is your own experience and, above all, properly sizing the server.
If I could, I'd definitely increase the RAM on mine...
-
Christophe
- Messages: 85
- Registration: June 5, 2018 - 8:31 AM
- Location: Arras (62)
- Contact :
Hi Julien,
So, my server has 8 vCPUs and 16 GB of RAM.
I'm experiencing console freezes when installing software on multiple PCs simultaneously, for example, when redeploying a computer lab. Also, sometimes not all the software installs at once (I install about fifty programs on the PCs).
But overall, it works.
I still think I'll have to switch to Linux.
So, my server has 8 vCPUs and 16 GB of RAM.
I'm experiencing console freezes when installing software on multiple PCs simultaneously, for example, when redeploying a computer lab. Also, sometimes not all the software installs at once (I install about fifty programs on the PCs).
But overall, it works.
I still think I'll have to switch to Linux.
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Christophe,
the console freezing issues and failed installations are largely related to the nginx problem on Windows. Switching to a Wapt Linux server, and if that's not enough, enabling uwsgi mode should greatly reduce, or even completely eliminate, these freezes given the size of your network.
We've also significantly improved console performance in the upcoming Wapt 2.7 release. However, on Windows, you'll still experience the nginx-related freezing issues.
Sincerely,
Denis
the console freezing issues and failed installations are largely related to the nginx problem on Windows. Switching to a Wapt Linux server, and if that's not enough, enabling uwsgi mode should greatly reduce, or even completely eliminate, these freezes given the size of your network.
We've also significantly improved console performance in the upcoming Wapt 2.7 release. However, on Windows, you'll still experience the nginx-related freezing issues.
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
