Roel Janssen <[email protected]> writes: > The NFS overhead is pretty large. Maybe we can better tune it, and if > so, document how to tune it for GNU Guix. I already talked to our > storage expert, and tuning boils down to using fast disks, a > large-enough NFS cache, and low-latency network equipment.
We may get a faster NFS share soon (with some of the slow storage settings disabled), but I don’t hold my breath when it comes to NFS performance. > The reason we have /gnu NFS-mounted on the build node is that we can > then very easily replace the node when it would have a hardware failure, > without even losing the ability to run programs that were already > installed. That’s the same reason I have for keeping /gnu on NFS. I have been experimenting with lsync (writing to local disks and then pushing changes asynchronously from local-gnu to remote-gnu), but I wasn’t convinced it would be reliable. I’m not sure if this would help, though, when the nodes keep mounting /gnu over NFS. Is there a way to put /gnu on a Samba share instead? I’d like to give that a try, but I’m not sure about what would happen to ownership and permissions (I don’t worry about hardlinks because I disabled deduplication). -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
