You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by "Khoe, Yonathan" <Yo...@unt.edu> on 2021/10/07 17:13:08 UTC
Recommended Implementation - Multiple Guac Servers Necessary?
Hello,
I jump abroad the Guacamole project at my university after a colleague from another college did. I got his insights into their college setup involving 1 web server and 2 guacd servers as backbone. I'm trying to get an understanding how/why this is necessary based on reading through the guac mailing archives. I see many utilize single, relatively high-performance server with room for scaling. If my college (1 college, not the entire university body) were to expect performance that is about 80-100 concurrent usage max, is it necessary to have the multi-server implementation in order to help with performance and reliability of our Guacamole service? Depending on the answer, do the "backbone" guacd servers have to be configured as proxy servers (something that's described in chapter 4 in the documentation)?
For context, I have set up my college with the following:
The server VM I have set up with apache tomcat and guacamole server:
* Xeon Gold 6140 CPU @ 2.30GHz (alloted 6 cores)
* 8GB RAM
* 80GB Storage
* Llvmpipe Graphics
* RHEL 8.4
* VMWare virtualization
The supposed GuacD server that's still a blank slate:
* Xeon Gold 6140 CPU @ 2.30GHz (alloted 12 cores)
* 16GB RAM
* 80GB Storage
* Llvmpipe Graphics
* RHEL 8.4
* VMWare virtualization
Thank you,
Yo Khoe
CVAD IT
University of North Texas
Re: Recommended Implementation - Multiple Guac Servers Necessary?
Posted by Ivanmarcus <iv...@yahoo.com.INVALID>.
Just to followup Mike's comments with an 'real world' example.
For some years I've supported an installation that has had upwards of
100 concurrent users. This was done via a single VM with 4 cores
allocated and (I think) 12GB RAM, there was no proxy server involved.
There have been essentially no performance issues attributable to
Guacamole with the above setup and occasional checks of the VM showed it
running well within capacity.
Typical client usage was fairly mixed between email/word processing/CAD
work, I suspect almost no-one used video...
On 8/10/21 12:24 pm, Mike Jumper wrote:
> Hello,
>
> You don't need multiple guacd servers, no. For 80-100 concurrent users,
> typical desktop use would require guacd to have around 4 CPU cores
> available, but it doesn't matter with respect to performance whether
> those 4 cores are split across multiple servers or all on the same
> server. Your planned 12-core server should have more than enough power
> to support your anticipated load.
>
> The main benefit to leveraging multiple guacd servers (behind a TCP
> balancer) is the ability to dynamically scale those servers and take one
> down if needed, and the main caveat for leveraging multiple guacd
> servers behind a balancer is that the balancer will prevent the screen
> sharing feature from working (there will be a random chance that the
> guacd the webapp is routed to by the balancer is not the guacd
> associated with the connection being joined).
>
> Michael Jumper
> CEO, Lead Developer
> Glyptodon Inc <https://glyp.to/>.
>
>
> On Thu, Oct 7, 2021 at 10:13 AM Khoe, Yonathan <Yonathan.Khoe@unt.edu
> <ma...@unt.edu>> wrote:
>
> Hello,____
>
> I jump abroad the Guacamole project at my university after a
> colleague from another college did. I got his insights into their
> college setup involving 1 web server and 2 guacd servers as
> backbone. I’m trying to get an understanding how/why this is
> necessary based on reading through the guac mailing archives. I see
> many utilize single, relatively high-performance server with room
> for scaling. If my college (1 college, not the entire university
> body) were to expect performance that is about 80-100 concurrent
> usage max, is it necessary to have the multi-server implementation
> in order to help with performance and reliability of our Guacamole
> service? Depending on the answer, do the “backbone” guacd servers
> have to be configured as proxy servers (something that’s described
> in chapter 4 in the documentation)?____
>
> __ __
>
> For context, I have set up my college with the following:____
>
> The server VM I have set up with apache tomcat and guacamole server:____
>
> * Xeon Gold 6140 CPU @ 2.30GHz (alloted 6 cores)____
> * 8GB RAM____
> * 80GB Storage____
> * Llvmpipe Graphics____
> * RHEL 8.4____
> * VMWare virtualization____
>
> __ __
>
> The supposed GuacD server that’s still a blank slate:____
>
> * Xeon Gold 6140 CPU @ 2.30GHz (alloted 12 cores)____
> * 16GB RAM____
> * 80GB Storage____
> * Llvmpipe Graphics____
> * RHEL 8.4____
> * VMWare virtualization____
>
> __ __
>
> __ __
>
> Thank you,____
>
> Yo Khoe____
>
> CVAD IT____
>
> University of North Texas ____
>
> __ __
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@guacamole.apache.org
For additional commands, e-mail: user-help@guacamole.apache.org
Re: Recommended Implementation - Multiple Guac Servers Necessary?
Posted by Mike Jumper <mi...@glyptodon.com>.
Hello,
You don't need multiple guacd servers, no. For 80-100 concurrent users,
typical desktop use would require guacd to have around 4 CPU cores
available, but it doesn't matter with respect to performance whether those
4 cores are split across multiple servers or all on the same server. Your
planned 12-core server should have more than enough power to support your
anticipated load.
The main benefit to leveraging multiple guacd servers (behind a TCP
balancer) is the ability to dynamically scale those servers and take one
down if needed, and the main caveat for leveraging multiple guacd servers
behind a balancer is that the balancer will prevent the screen sharing
feature from working (there will be a random chance that the guacd the
webapp is routed to by the balancer is not the guacd associated with the
connection being joined).
Michael Jumper
CEO, Lead Developer
Glyptodon Inc <https://glyp.to/>.
On Thu, Oct 7, 2021 at 10:13 AM Khoe, Yonathan <Yo...@unt.edu>
wrote:
> Hello,
>
> I jump abroad the Guacamole project at my university after a colleague
> from another college did. I got his insights into their college setup
> involving 1 web server and 2 guacd servers as backbone. I’m trying to get
> an understanding how/why this is necessary based on reading through the
> guac mailing archives. I see many utilize single, relatively
> high-performance server with room for scaling. If my college (1 college,
> not the entire university body) were to expect performance that is about
> 80-100 concurrent usage max, is it necessary to have the multi-server
> implementation in order to help with performance and reliability of our
> Guacamole service? Depending on the answer, do the “backbone” guacd
> servers have to be configured as proxy servers (something that’s described
> in chapter 4 in the documentation)?
>
>
>
> For context, I have set up my college with the following:
>
> The server VM I have set up with apache tomcat and guacamole server:
>
> - Xeon Gold 6140 CPU @ 2.30GHz (alloted 6 cores)
> - 8GB RAM
> - 80GB Storage
> - Llvmpipe Graphics
> - RHEL 8.4
> - VMWare virtualization
>
>
>
> The supposed GuacD server that’s still a blank slate:
>
> - Xeon Gold 6140 CPU @ 2.30GHz (alloted 12 cores)
> - 16GB RAM
> - 80GB Storage
> - Llvmpipe Graphics
> - RHEL 8.4
> - VMWare virtualization
>
>
>
>
>
> Thank you,
>
> Yo Khoe
>
> CVAD IT
>
> University of North Texas
>
>
>