Re: WIO delays with SSHFS

Hi Rolf,

We've been running dozens of wine programs on thin and fat clients for 
more than a decade in 1000+ Greek schools without seeing this issue at 
all. We're not using localapps/remoteapps but I don't think it would 
make a difference.

I *suspect* that you're using some specific programs that have issues 
with sshfs and file locks etc. If that's the case, you should either 
pinpoint the issue and report it to the wine or sshfs developers,
or you could try switching to nfs home, which supports file locks better.

But that's just an assumption, as I have no programs that misbehave this 
way (except for gnome-keyring which isn't a wine program).

Btw, in general, if anyone needs professional (paid) support and thinks 
I might be able to help, feel free to P.M. me even if they're not 
related to LTSP.

Cheers,
Alkis


On 10/29/19 9:56 AM, Rolf-Werner Eilert wrote:
> Here is an update to that issue. Maybe it's important to keep that in 
> mind for the new LTSP too.
> 
> During the holidays, I changed all users' icons pointing to Wine 
> programs so they include "Exec=ltsp-remoteapps ...". And as I had 
> expected, students can start their programs now. As long as there are 
> only one or two of them starting at the same time, it starts even much 
> faster than as a strictly local app.
> 
> However, there still was a bit of a delay when too many (i. e. about > 
> 4) students would start their Word or whatever at the same time. 
> Sometimes they got unpatient and clicked once more, causing even more 
> delays. So I tried to find out the reason for the delay.
> 
> I used iotop and found that it's caused by sshd and sshfs. Whenever a 
> Wine (or Crossover) app is started, never mind whether as a remote app 
> or not, it causes a number of WIO delays which force the CPU to wait 
> (for whatever). When starting a local app on the fat client, it will 
> cause WIOs on the client AND on the server. When started as a remote app 
> on the same client, it will start WIOs on the server only.
> 
> Meanwhile I am thinking about installing the whole thing on our old 
> server which has much more CPUs and RAM and could balance such peaks 
> much better than the current small server which is actually merely a 
> standard office PC and was planned to serve for local apps only.
> 
> But of course I would try the new LTSP on the other server. So my 
> question is, can you make a guess if this problem still is there on LTSP 
> 19, or maybe you are sure it doesn't exist there anymore?
> 
> Regards
> Rolf
> 


_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net