I am also interested in this. So far, small tests show that it will vary greatly based on the user activity. Most of the overhead is produced by the guacd daemon handling the connections and compressing images. This is almost entirely CPU heavy and will require more or less computing depending on the amount of colors in the RDP session and how frequently they change. For example, watching a youtube video over RDP in the browser is brutal on CPU. I recommend having a cluster of servers running Debian MINIMAL INSTALL for nothing but instances of guacd (and use 0.9.12's new load balancing feature).
You can additionally separate the angularjs front end application and guacamole-common-js API, as well as the MySQL (or whatever auth you use) server. My setup looks like this: FW --> NGINX HA cluster--> custom ASP.NET/AngularJS app with guacamole integrated (cluster) --> MySQL/AD --> guacamole-common-js/guacamole-common-java/Tomcat (buffed resources, cannot cluster) --> Debian/guacd *RESOURCE HEAVY* (cluster) --> virtual hosts Let me know if you want some advice! -- View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/Guacamole-performance-in-bigger-environment-and-setup-tp989p1019.html Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
