Peter, are you using nginx as a reverse proxy inbound into Guacamole?
I've tried doing that here with Guacamole doing RDP to a separate
Windows server and it's really draggy whereas browsing directly into
Guacamole in Tomcat is not. With nginx performing the redirect, it's
draggy enough that no users are going to be happy with it.
Tomcat/Guacamole and nginx are running on the same machine here but it's
not loaded up at all when the connection is present so I wonder if it's
just a function of how nginx behaves with HTML5 traffic the way
Guacamole is painting it.
Thanks,
- Jeff
On 6/17/20 5:28 AM, Peter De Tender wrote:
Hi all,
To add on this, I’m seeing the same behavior on my systems (running as
Azure VMs), for our lab scenarios:
* 20 students using RDP to Windows 2016 Server
* Active sessions 7hours a day, with about 4h “active use” (standby
online when trainers are presenting)
* Azure VM Size: D2sv3 (Xeon E5-2673 2.4Ghz), 2 CPU / 8GB RAM / 4
SSD drives
* Average load is about 20% CPU throughout the day, 3,7GB RAM
FYI, this is a single VM setup with MariaDB and NGINX, running behind
Azure Front Door SSL Gateway with WAF.
Thx, Peter
*From:*ivanmarcus <[email protected]>
*Sent:* Wednesday, June 17, 2020 7:31 AM
*To:* [email protected]; lynnaj <[email protected]>
*Subject:* Re: Server specifcations?
This is a question that's come up a few times.
Mike's recommendation is that you "generally need 1 core and 2 GB for
every 25 concurrent users at peak" (ref this thread:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/Guacamole-System-Resource-requirements-for-better-performance-td5996.html).
In the half-dozen installations I have this fits in with my experience
too. As far as I'm aware no-one has expressed any contrary view.
With regard to disk sizing, I generally run my installations as a VM
with dynamic sizing up to ~20GB. Most use less than 3GB in practice.
Network bandwidth is more difficult to determine, it will depend upon
a number of factors around what it is your users are doing, and how
you have things set up. There have been various discussions on this
too; I suggest having a look at the mailing list referenced above as
you may find someone with a use-case similar to yours. This thread may
be helpful as a start:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/Viewing-active-connections-while-using-user-mapping-xml-td7844.html#a7861
In general it's fair to say that Guacamole does a good job with
compression, and bandwidth requirements are not too onerous.
On 17/06/2020 4:02 a.m., lynnaj wrote:
Hello All -
I can't seem to find anything recent online about Guacamole server
specifications/recommendations.
What size/type of server(s) are you running this on and for how many
concurrent connections? How much memory? How many and what types of CPU(s)?
How much disk space? How much network bandwidth?
What am I missing?
Thank you.
- Lynna Jackson, Williams College
--
Sent
from:http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
---------------------------------------------------------------------
To unsubscribe, e-mail:[email protected]
<mailto:[email protected]>
For additional commands, e-mail:[email protected]
<mailto:[email protected]>
