guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: Guacamole Performance
Date Thu, 18 Aug 2016 07:12:43 GMT
Hi Mike,

The tool I was talking about is just a web application that launches the vnc sessions on the
requested resource and passes the authentication details to guacamole.
To eliminate some possibilities, I’ve just installed guacamole (without the tool and built
from the source on apache github) on a fresh Debian Jessie VM and the performance is still
subpar to turbovnc viewer.

The VM itself has 2 cores with 4 GB of ram with a 1gbit network to my laptop. I’ve been
watching the cpu and mem usage and it doesn’t seem to be bottlenecking the performance.
I’m connecting to a turbovnc server on the same VM but I’ve tried different remote machines
Guacamole is running inside tomcat and I’m using apache for the websocket proxy.

Also, I mentioned in my original email that I wasn’t able to set the size of the session
to 100% without resizing the web browser window itself. Am I missing something obvious? The
image looks a lot sharper and much easier to look at when it is not being stretched.

Is there anything else you recommend for me to try?


From: Mike Jumper []
Sent: Friday, 12 August 2016 1:48 PM
Subject: Re: Guacamole Performance

On Thu, Aug 11, 2016 at 7:47 PM, <<>>
Hi Shanon,

I’m not sure about the version numbers but I cloned guacamole-client and guacamole-server
directly from about a month ago so it should be pretty recent.

The latest development will be on the Apache repositories, so definitely try against those:

A month ago is after the point where Guacamole was accepted into the Apache Incubator, so
there's a good change the code you cloned was actually closer to ~6 months old.

That said, even that old should be fine ... 0.9.9 happened before that and was a very decent
release, and quite fast.

I should probably clarify that turbovnc runs without issues, it’s only guacamole.

Is there anything else you can tell us about your setup?

What does your network look like? What kind of machine is serving Guacamole? Are you using
Tomcat or some other servlet container? Are there any proxies involved? etc.

You say that you're using a Guacamole-based tool. What differs here between the tool (what
tool?) and a stock Guacamole deployment?

Any additional information about the deployment details of guac would be helpful.

- Mike

View raw message