Re: Porting GNOME to Wayland NFS performance in GNOME 3

["stefan skoglund(agj)" <stefan skoglund agj net>]

mån 2013-03-18 klockan 09:10 -0700 skrev Sriram Ramkrishna:
>

On Mon, Mar 18, 2013 at 7:58 AM, stefan skoglund(agj)
<stefan skoglund agj net> wrote:
>         fre 2013-03-15 klockan 14:32 -0400 skrev Matthias Clasen:
>         
>         
>         I dont think Redhat wants to have the same type of
>         conversation they had
>         with an client about GVFS bad behaviour when running over NFS
>         if an
>         wayland compositor is sensitive to the same type of race
>         condition as
>         gvfsd.
>         
>
>
> In general, using NFS is a bad idea for a desktop in any case.  As you
> say there is any number of conditions due to locking that could cause
> race conditions.
>  
>
>         OR is the gnome community of the belief that NFS-accessed home
>         directories is obsolete ?
>         The race condition in gvfsd can be triggered in the use case
>         of a single
>         user desktop on a single machine but said machine needs to be
>         heavily
>         loaded.
>         
>
>
> Speaking of someone who has been in a very large enterprise
> environment where our home directories were all NFS mounted, we never
> ran into these issues.  Why?  Because we all ran fvwm and not a full
> blown desktop OS.

I have a university lab setup with gnome 3.6 desktop environment in
debian wheezy and Kerberized NFS-access to the home directory (the
server is a Nexenta Appliance.) It is enough to say that login
performance is abysmal. I think this steems from the heavy usage of
dconf at login-time (at least 1 minute from login in gdm to a working
desktop.) This is on 4 year old HP AMD64 hardware and intel i745 (?)
hardware.

I occasionally also have a bit of trouble with Pulseaudio's .pulse
directory in this environment.

A pristine KDE in the same setup has very nice login performance so do
enlightenment (of course.)

The RedHat thing is a really longlived bug in redhats bugzilla about
gvfs metadata induced overload of NFS servers. That bug is rather bad
and i think that if it isn't resolved it will make GNOME3 impossible to
run in NFS-environments.
I hope that Weston (for example) doesn't create a situation like that
but i'm pessimistic.