Re: Full Report: LTSP Hackfest Portland 2008

hi,
Am Mittwoch, den 30.07.2008, 18:54 -0700 schrieb Donnie Berkholz:
> Has anyone tried NFSv4 lately? It's supposed to have much-improved 
> caching, at least in recent kernels.
i tinkered a bit with it when i researched methods for boot speedup and
back then it didnt really provide to be a speed improvement and has a
way more complicated way to set it up. the kerberos integration and
enhanced security it offers are indeed tempting factors, but in the end
i decided to go for nbd which works fine with aufs as well btw (ubuntu
dropped unionfs in intrepid (8.10) in favor of it). vagrant did some
research on the nbd copy on write feature which should make nbd very
intresting for distros not shipping either of the uniting filesystems
and i imagine that if you put the cow part of the image into a tmpfs it
might even be faster than the nbd/aufs solution (but require some more
ram server side indeed).

also very intresting is to use nbd swap in a server side tmpfs, you can
even get 16-24M clients working smoothly with all features enabled (but
a 128M tmpfs for every client raises the server ram requirements in a
pretty significant way and i didnt try with more than 5 clients, not
sure when your network saturates here, but nontheless something we
should probably document)

ciao
	oli

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIkY+NSsOT+6LQaTYRAgVRAJ0WXaBYTxxNvakHZbRe2u4FpZ6x6QCfXZyo
kemuqjouBE7ku03MAPdYSpc=
=foCQ
-----END PGP SIGNATURE-----