slow when $HOME is served over NFS

[David Roundy]

xpra evidently creates a largish file under ~/.xpra, and does considerable IO to it. This causes xpra to run very slowly when $HOME is on an NFS file system.

I haven't looked to see what this file is used for, but at a minimum it would be good to be able to specify a different directory for it. As it is, xpra is so slow as to be close to useless for me, and contributes considerable load to the NFS server. I could run xpra on the server, but that would also add load to that machine, when I'd rather put the load on my own workstation.

[Antoine Martin]

Hmm, there should not be much traffic to the logfile and my log files are reasonably small, what's the contents of yours?

(I'll add the option of specifying the logfile location)

[David Roundy]

I can't see it now, but what made me suspicious was a .nfsXXX file that was over 300 meg in .xpra/, which usually would mean that a file had been created and then deleted while a file handle was still accessing it. I figured you were creating temporary files there.

The log file is just a few hundred k, and I can attach it if you like. I'm starting up xpra to see if I can observe the same behavior.

[Antoine Martin]

300MB is suspiciously close to the size of the memory mapped file it used to create in ~/.xpra prior to r390, this now goes in $TMPDIR or /tmp.

This change is part of v0.0.7.33 and later.

[David Roundy]

Good news, thanks! I'm indeed using the xpra 0.0.7.31 that is packaged in Debian testing and backported to Debian stable. I see that 0.0.7.26 is already packaged for sid, so expect to get the fix soon that way.

[Antoine Martin]

OK, closing - feel free to re-open if it still occurs with 0.0.7.36 or later.

(I'll assume you meant 36 not 26..)

[migration script]

this ticket has been moved to: ​https://github.com/Xpra-org/xpra/issues/80