Re: Slow output - Linux connections

[Ivanmarcus]

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: user-unsubscr...@guacamole.apache.org
For additional commands, e-mail: user-h...@guacamole.apache.org

Re: explicit error message

[Nick Couchman]

On Thu, Oct 19, 2023 at 9:01 AM miao  wrote:

> Thx a lot.
> I have read some guacamole client source code.  I feel uncertain about the
> error code in file named ‘en.json’ .
>
> ```
>
> ERROR_CLIENT_202
>
> ERROR_CLIENT_207
>
> ```
>
> The code like 207 is means guac_code? There is enum named as
> GuacamoleStatus. Am I right?
>

Yes, these are Guacamole protocol errors. The translation between these and
the upstream (VNC, for example) errors is done in the guacd source code,
within the source code for each protocol (src/protocols/vnc/vnc.c, in the
case of VNC). The ability to do that translation relies on the client
library, libvncclient in the case of VNC, as Mike mentioned, being able to
provide meaningful feedback on what has gone wrong in the actual connection
to the server. Since, as Mike mentioned, libvncclient's "rfbInitClient"
function provides no detail at all on why the connection failed, we have no
way of knowing what actually failed and so cannot provide any meaningful
error message translation between VNC and Guacamole.

-Nick

Re: explicit error message

[miao]

Thx a lot. 
I have read some guacamole client source code.  I feel uncertain about the 
error code in file named ‘en.json’ .

```
ERROR_CLIENT_202
ERROR_CLIENT_207
```

The code like 207 is means guac_code? There is enum named as GuacamoleStatus. 
Am I right?



> 2023年10月18日 23:38，Michael Jumper  写道：
> 
> On 10/17/2023 8:02 PM, miao wrote:
>> Hi all!
>> I am connecting a vnc app. It works well normally.  But, when I give wrong 
>> pwd or wrong ip host, guac return same error message as “The remote desktop 
>> server is currently unreachable”.
>> If possible, can we make explicit error message? Authentication error and 
>> network error.
> 
> This is not currently possible as the underlying VNC library (libvncclient) 
> does not provide a mechanism for determining the cause of a connection 
> failure. It exposes only whether the connection was successful/failed, but no 
> machine-readable specifics regarding the failure.
> 
> - Mike
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
> For additional commands, e-mail: user-h...@guacamole.apache.org

RE: Slow output - Linux connections

[Julien Lejeune]

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.

-Message d'origine-
De : Luke H  
Envoyé : mercredi 18 octobre 2023 11:03
À : user@guacamole.apache.org; Julien Lejeune 
Objet : RE: Slow output - Linux connections

Agreed on all counts! Nick, thank you so much for regularly reviewing this 
list, responding, and playing such a large role in what Apache Guacamole is and 
will be. AG is incredibly well thought out and feature rich. With its license, 
it will have longevity. Meaning, for us tech people, it is a solid technology 
to add to one's portfolio.

One last detail for you Julien. As stated earlier, this is fascinating, and 
there is one more result I want to show - VNC. In order of shortest times for 
the BIGFILE.txt test:

$ dd if=/dev/urandom bs=1024k count=1024 | base64 > BIGFILE.txt $ time cat 
BIGFILE.txt

# Guacamole/VNC
0.000u 1.367s 0:24.99 5.4%  0+0k 267856+0io 0pf+0w

# Direct SSH connection
0.008u 2.280s 2:18.43 1.6%  0+0k 0+0io 0pf+0w

# Guacamole/SSH
0.006u 2.150s 4:39.53 0.7%0+0k 0+0io 0pf+0w

I am not exactly sure how to interpret this counterintuitive VNC speed, but I 
sense that latency you see is governed not by Guacamole, but by the supporting 
connection library.

The short answer to this discussion then, would be: it's probably a library 
dependency, and not related to Guacamole, nor Linux.

Luke

PS - These Guacamole numbers were generated with libssh2-1.11.0 and 
libvncserver-0.9.13.

> On 10/18/2023 2:20 AM CDT Julien Lejeune  wrote:
> 
>  
> Hi Nick,
> 
> Thank you for your feedback.
> I understand and I totally agree with everything you wrote.
> 
> On that note, I am very happy with Guacamole, its features, and its 
> performances so far.
> At my company, we manage servers hosted all around the world from the same 
> Guacamole instance and this « cat » issue is the only latency problem I have 
> encountered so far. I am impressed by this product and the work that has been 
> done on it.
> 
> As you said, the real way to fix my problem is to kindly remind my colleagues 
> not to use « cat » on big files. That’s bad practice.
> This latency latency I wrote about is only a technical symptom of this human 
> problem.
> Nonetheless, I am excited to work with Guacamole and to understand it inside 
> out. I felt digging into this latency issue would be a great opportunity to 
> learn about this product. And I felt sharing it was a nice way to connect to 
> this project’s community.
> 
> Best regards,
> 
> Julien Lejeune
> IT administrator
> 
> +32(0) 81 33 11 11
> www.actia.be [Linkedin] 
> 
> 
> 
> 
> 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