> > We wrote our own client, using guacamole-common-js (also version 1.0.0). > Websockets the client app opens against the web server go through AWS ALB > and then through eBay's Fabio load balancer (they also expose the web > server as HTTPS). > > I'd start, here, looking at this. If you wrote your own client, it's possible something is going on there that is sub-optimal and causing issues. Have you tried the same connection load to the same systems using the official Guacamole Client? You don't have to use it long-term - Guacamole is designed to be used in applications that you write/design, but for the purposes of performance testing and debugging, it might be useful to at least try out the Guacamole Client with the same load level and see if the problems are the same.
> 7. We do see that upon connecting, both the guacd container and the web > server container have CPU load (it could be higher than 100% utilization > when opening ~20 connections). > The specs of the containers themselves: > guacd runs with 2000mhz / 6gb / 30mbits. > The web server runs with 2000mhz / 2gb / 10mbits. > > I suspect that this is really at the root of all of the issues you are having - if you're seeing > 100% CPU utilization on both your guacd and Tomcat compute instances, then much of the other behavior you've described could be attributed to "resource starvation" - the inability of the guacd threads and/or Tomcat to get timely access to the CPU that it needs. Again, I'd advise trying out the official Guacamole Client with these same resource levels and same connection load and see what happens - is the resource utilization at the same level, and do the same symptoms show up. Also, you mention high CPU utilization, here, but have you checked on memory utilization, as well? -Nick
