Julien, Thanks for taking the time to post this in detail.
As performance and hardware requirements are a question that arises from time to time such practical information will be very useful for some.
On 19/10/23 23:35, Julien Lejeune wrote:
Hi all! It will probably be my last update on the subject. Short version: I have solved this latency problem by deploying a new Guacamole server on better hypervisors. For those interested in the details, my Guacamole server was hosted on a small VMware cluster of two ESXi servers. The resources (CPU/RAM) of those ESXi servers are OK and all services hosted on them seemed to work fine. Those ESXi have old hardware that is not supported by VMware anymore. Compared to my production ESXi servers, they have fewer CPU (32 vs 96), slower CPU (2~2.6Ghz vs 3Ghz) and less network bandwidth (aggregated 1G vs aggregated 10G). So I deployed a new guacamole server (and its DB) on my production cluster. I have compared the execution time of the cat command on a big file and the improvement was significant. - 56 seconds from the first Guacamole server running on management ESXi. - 10~15 seconds from the new GUacamole server running on production ESXi. The "cat" is still bad practice, but it was a good way to measure the improvement. On my new Guacamole server, I can use the "less" command without seeing any latency I had seen with the previous server. Looking back at it, some of the services hosted on our management cluster have required some tuning to improve their performances. Each of those was addressed separately because they were individual projects. This latency issue has given me the chance to have a holistic understanding of our projects, tools, and infrastructure. I have tried to install a newer version of libssh2 (1.11.0 instead of 1.8.0) but it didn't improve the execution time on the new server. So I'll stick with the version available in the Ubuntu repository. Thanks for all your feedback. Best regards, Julien Lejeune IT administrator +32(0) 81 33 11 11 www.actia.be This email message as well as all attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
