You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Jacob Staub <jp...@gmail.com> on 2017/05/10 02:20:49 UTC
0.9.12 slowing to a crawl over a period of 5 to 10 minutes of use
Hello,
Thank you for all the good work on Guacamole.
I am having trouble with 0.9.12 slowing to a crawl over a period of 5 to
10 minutes of use in a reverse proxy application. I upgraded from 0.9.9
for the ability to screen share but found 0.9.12 so unstable that I
returned to 0.9.9 which produces solid operation using the same proxy
settings that were established for 0.9.12. The environment under which
guacamole operates:
Server = Ubuntu 16.04.2 LTS
Docker = 17.03.1-ce
Docker-compose = 1.13.0
jwilder/nginx-proxy = 1.13.0 <https://github.com/jwilder/nginx-proxy>
database flavor = postgresql
Connection OS = Windows7
Proxy settings were implemented as described under Chapter 4
<https://guacamole.incubator.apache.org/doc/gug/proxying-guacamole.html#proxying-with-apache>.
The database of 0.9.12 is an upgrade of the 0.9.9 database if that makes
any difference.
What I could use is assistance with diagnosing what might cause
guacamole to bog down over time in 0.9.12. It doesn't seem like
something related to configuration given 0.9.9 appears to work fine in
the same environment.
Regards,
Jake
Re: 0.9.12 slowing to a crawl over a period of 5 to 10 minutes of use
Posted by Jacob Staub <jp...@gmail.com>.
Good evening Mike,
I spun up a 0.9.12 Guacamole instance this evening. See attached
recording of the performance under Firefox. The behavior of Firefox
under 0.9.12 is a lot different as compared to 0.9.9. When the system
starts freezing up the frame rate pegs near 60 fps and doesn't relax.
Again, I don't know enough about webapps to tell if this is due what
I've done on setup or whether it's inherent in the way Guacamole 0.9.12
is interacting with the system as a whole.
Screen sharing is what I'm really after with 0.9.12. Would you recommend
giving 0.9.10 a try or is the architecture so similar that it's likely
the end result will be the same as 0.9.12?
Regards,
Jake
On 5/9/2017 10:39 PM, Mike Jumper wrote:
> What protocol is being used between guacd and the remote desktop in
> this case?
>
> Do you see any interesting specific differences with 0.9.9 vs 0.9.12
> on either the guacd side or the browser side regarding memory
> consumption, swap usage, or CPU usage?
>
> - Mike
>
>
> On Tue, May 9, 2017 at 7:20 PM, Jacob Staub <jpstaub1@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hello,
>
> Thank you for all the good work on Guacamole.
>
> I am having trouble with 0.9.12 slowing to a crawl over a period
> of 5 to 10 minutes of use in a reverse proxy application. I
> upgraded from 0.9.9 for the ability to screen share but found
> 0.9.12 so unstable that I returned to 0.9.9 which produces solid
> operation using the same proxy settings that were established for
> 0.9.12. The environment under which guacamole operates:
>
> Server = Ubuntu 16.04.2 LTS
> Docker = 17.03.1-ce
> Docker-compose = 1.13.0
> jwilder/nginx-proxy = 1.13.0 <https://github.com/jwilder/nginx-proxy>
> database flavor = postgresql
> Connection OS = Windows7
>
> Proxy settings were implemented as described under Chapter 4
> <https://guacamole.incubator.apache.org/doc/gug/proxying-guacamole.html#proxying-with-apache>.
> The database of 0.9.12 is an upgrade of the 0.9.9 database if that
> makes any difference.
>
> What I could use is assistance with diagnosing what might cause
> guacamole to bog down over time in 0.9.12. It doesn't seem like
> something related to configuration given 0.9.9 appears to work
> fine in the same environment.
>
> Regards,
> Jake
>
>
>
>
>
Re: 0.9.12 slowing to a crawl over a period of 5 to 10 minutes of use
Posted by Jacob Staub <jp...@gmail.com>.
Good morning Mike,
The guacamole containers are configured for jwilder/nginx-proxy such
that http is available for users operating on the local network and
https is used when making connections via the wide network.
For a while it seemed like the slow down behavior could be bypassed in
the local setting by hair pinning via https. While a bit more useful
time (say ten minutes instead of five) was gained for the end user
before slow down the connection still slowed to a crawl in the end.
In my original email I neglected to state that the browser is Firefox 53
(32bit) running on a mix of Mac and Windows machines. I don't recall
trying a different browser although in hindsight it's a logical piece of
troubleshooting that was neglected if it wasn't tried.
I'll admit that computer development is not my bag so I didn't think to
hunt down memory consumption etc. I took a quick look at 0.9.9
performance this morning via Firefox development tools. For 0.9.9:
Primed cache = 807KB, Empty cache=807KB, and a snapshot of performance
is included which was taken at time when the average frame rate was
approximately 30fps.
Since the browser stuff was easy to gather I'll collect the same for
0.9.12 when I get a chance.
Regards,
Jake
On 5/9/2017 10:39 PM, Mike Jumper wrote:
> What protocol is being used between guacd and the remote desktop in
> this case?
>
> Do you see any interesting specific differences with 0.9.9 vs 0.9.12
> on either the guacd side or the browser side regarding memory
> consumption, swap usage, or CPU usage?
>
> - Mike
>
>
> On Tue, May 9, 2017 at 7:20 PM, Jacob Staub <jpstaub1@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hello,
>
> Thank you for all the good work on Guacamole.
>
> I am having trouble with 0.9.12 slowing to a crawl over a period
> of 5 to 10 minutes of use in a reverse proxy application. I
> upgraded from 0.9.9 for the ability to screen share but found
> 0.9.12 so unstable that I returned to 0.9.9 which produces solid
> operation using the same proxy settings that were established for
> 0.9.12. The environment under which guacamole operates:
>
> Server = Ubuntu 16.04.2 LTS
> Docker = 17.03.1-ce
> Docker-compose = 1.13.0
> jwilder/nginx-proxy = 1.13.0 <https://github.com/jwilder/nginx-proxy>
> database flavor = postgresql
> Connection OS = Windows7
>
> Proxy settings were implemented as described under Chapter 4
> <https://guacamole.incubator.apache.org/doc/gug/proxying-guacamole.html#proxying-with-apache>.
> The database of 0.9.12 is an upgrade of the 0.9.9 database if that
> makes any difference.
>
> What I could use is assistance with diagnosing what might cause
> guacamole to bog down over time in 0.9.12. It doesn't seem like
> something related to configuration given 0.9.9 appears to work
> fine in the same environment.
>
> Regards,
> Jake
>
>
>
>
>
Re: 0.9.12 slowing to a crawl over a period of 5 to 10 minutes of use
Posted by Mike Jumper <mi...@guac-dev.org>.
What protocol is being used between guacd and the remote desktop in this
case?
Do you see any interesting specific differences with 0.9.9 vs 0.9.12 on
either the guacd side or the browser side regarding memory consumption,
swap usage, or CPU usage?
- Mike
On Tue, May 9, 2017 at 7:20 PM, Jacob Staub <jp...@gmail.com> wrote:
> Hello,
>
> Thank you for all the good work on Guacamole.
>
> I am having trouble with 0.9.12 slowing to a crawl over a period of 5 to
> 10 minutes of use in a reverse proxy application. I upgraded from 0.9.9 for
> the ability to screen share but found 0.9.12 so unstable that I returned to
> 0.9.9 which produces solid operation using the same proxy settings that
> were established for 0.9.12. The environment under which guacamole operates:
>
> Server = Ubuntu 16.04.2 LTS
> Docker = 17.03.1-ce
> Docker-compose = 1.13.0
> jwilder/nginx-proxy = 1.13.0 <https://github.com/jwilder/nginx-proxy>
> database flavor = postgresql
> Connection OS = Windows7
>
> Proxy settings were implemented as described under Chapter 4
> <https://guacamole.incubator.apache.org/doc/gug/proxying-guacamole.html#proxying-with-apache>.
> The database of 0.9.12 is an upgrade of the 0.9.9 database if that makes
> any difference.
>
> What I could use is assistance with diagnosing what might cause guacamole
> to bog down over time in 0.9.12. It doesn't seem like something related to
> configuration given 0.9.9 appears to work fine in the same environment.
>
> Regards,
> Jake
>
>
>
>
>