Hello, This is something that I've noticed through various installation of Guacamole on different hardware spec servers. At the start of the Tomcat.service running, browsing around is snappy, but eventually clicking on different elements on the web interface (ex.: visiting the Settings page or clicking on the connection to start a remote session) takes an awfully long time. I do notice that some time, the animated gears do appear to indicate that the web page is loading content; while any other time, there is no indicator at all to let the user know what the web interface item that they clicked on is suppose to lead them somewhere (the web browser didn't have a spinning loading indicator, etc.). Users are expected to sit there until there is a response that lead them to the next interface/page.
In terms of # user accounts, we do have about 40k users that is stored in the database. I'm seeing this as the only reason why Tomcat could be slow or noninteractive to respond. Is that a valid theory? Is there any way to improve the browsing experience while going through the web pages in general? Some kind of best practice performance tuning? Thanks Yonathan Khoe Senior Systems Administrator CVAD IT University of North Texas 940.565.4793 yonat...@unt.edu<mailto:yonat...@unt.edu> https://itservices.cvad.unt.edu/
