Hmm, my only other avenue when looking at it to diagnose our issues was our network engineer doing packet inspection on all LAN traffic or just the applications our users were using were too intensive ( I can't see that being the case, though it is very old software that requires at minimum 20-30+ Xterm windows open)

On Tue, Jun 13, 2017 at 4:36 PM, Robert Dinse <nanook@eskimo.com> wrote:

     I only have 20mbit/s from home and 100mbit/s at co-lo and is working
fine, so 2.3gb should be more than adequate.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
 Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
   Knowledgeable human assistance, not telephone trees or script readers.
 See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Tue, 13 Jun 2017, brian town wrote:

Date: Tue, 13 Jun 2017 16:33:43 -0400
From: brian town <briantownjr@gmail.com>
To: Walid MOGHRABI <w.moghrabi@servicemagic.eu>
Cc: x2go-user <x2go-user@lists.x2go.org>
Subject: Re: [X2Go-User] X2Go vs. XRDP


The thin client point was only to express my setup as well and the findings
I had with x2go/VNC/NX/etc. I believe it to be more of a bandwidth issue,
as our bandwidth in our LAN is only giving out 2.3gb right now

On Tue, Jun 13, 2017 at 12:16 PM, Walid MOGHRABI <w.moghrabi@servicemagic.eu
wrote:

Brian, I don't really understand your point about your thin clients, LTSP
images and remote connection to RedHat VMs.

>From what I can tell, the lower spec thin clients we have are older Wyse
celeron based with 1Gb of RAM.
My thin client boot from LAN with the TCE-NG setup and simply download a
230MB OS image and run from it diskless.
They start the X2Go client in display manager mode and eat about 512MB
RAM, OS image included (running apps goes for about 200MB).
Since it's direct X2Go connection, there is no local stuff, only remote
and these low specs Thin Clients perform as good as the higher specs PCs we
converted to Thin Clients and which are 4GB, Core i3/i5 and more ...


Regards,
Walid Moghrabi

TRAVAUX.COM
BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403
13591 AIX EN PROVENCE CEDEX 3

----- Mail original -----

De: "brian town" <briantownjr@gmail.com>
À: "Daniel Lindgren" <bd.dali@gmail.com>
Cc: "x2go-user" <x2go-user@lists.x2go.org>
Envoyé: Mardi 13 Juin 2017 15:57:57
Objet: Re: [X2Go-User] X2Go vs. XRDP


I agree with Walid about XRDP being super fast and snappy with low
resource intensive desktops. It worked really well for me with a XFCE set
up on one project I was working on. However both XRDP and X2GO could not
provide a good visualization for my current project that has thin clients
pulling down LTSP images. The LTSP desktop images are all low resource but
we use them as a jumping point to connect to Red Hat VMs. The only
connection method I found that could support a decent desktop experience
for our users as with X11VNC + XDMCP. I went through xrdp/x2go/NX and even
Horizon View and all had either poor performance or in the case of Horizon
View were just not really meant for Linux yet (the support is pretty awful).


On Tue, Jun 13, 2017 at 9:40 AM, Daniel Lindgren < bd.dali@gmail.com >
wrote:



Hi all,


I have used both xrdp and X2Go for a few years, just personal use, not
professional/work related.


I've recently upgraded to Debian 9 with KDE Plasma 5 and had some issues
with X2Go, checked the wiki and found that Plasma 5 is unsupported at the
moment. I researched alternatives and discovered ThinLinc.


It's a commercial software, but free for home use up to 5 concurrent
users. Works with Plasma 5 and performance is good, at least for my use
case.


When/if X2Go gains support for Plasma 5 I may go back, but for now I can't
use it.


Cheers,
Daniel
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user




_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
---
DISCLAIMER: This e-mail is private and confidential and may contain
proprietary or legally privileged information. It is for the intended
recipient only. If you have received this email in error, please notify the
author by replying to it and then destroy it. If you are not the intended
recipient you must not use, disclose, distribute, copy, print or rely on
this e-mail or any attachment. Thank you