Date: Sat, 15 Jan 2000 00:59:16 -0500 From: Rod Taylor <rod@zort.on.ca> To: Matthew Dillon <dillon@apollo.backplane.com>, freebsd-current@freebsd.org Subject: Re: Thoughts... Message-ID: <0001150100540J.04098@rbtBSD.intranet> In-Reply-To: <200001150555.VAA96077@apollo.backplane.com> References: <0001150016090H.04098@rbtBSD.intranet> <0001150041180I.04098@rbtBSD.intranet> <200001150555.VAA96077@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok... You've mostly convinced me. On Monday I'll pick up a few boxes and test them out. Thanks for your information... On Sat, 15 Jan 2000, you wrote: > :Their current solution is to copy a 1.8GB disk image across the network onto > :the drives and use that as a normal local disk. The copy time takes several > :minutes. If for some reason 50 people decided to do this at the same time you > :could see where some network lag would come from. > > There are lots of ways of syncing up that do not require sending the > entire image over the network every time. Syncing is something you could > do with an NFS mount quite easily, combined with something like cpdup > (see /usr/ports/sysutils/cpdup). > :The other reason has to do with the laggy network and booting off it. The > :things not even 10MB switched per station. 8 workstations share 10mbit hubs. > :Netscape for example would take ages to load over NFS that way. (Afterall, in > :a class like that they tend to do everything in unison). > : > :Mounting / under NFS on the other hand doesn't appear that it would be trouble. > :It's /usr/local/bin that could use a little local caching. > > Using NFS for /, /usr, and /usr/local/bin over a slow 10BaseT network > being shared with many other clients is going to depend heavily on the > amount of memory the laptops have. NFS is very good at caching binaries > on the client if the client has sufficient memory. If the client does not > have sufficient memory then every time you run a binary it will have > to load it from the server. > > The NFS server will need enough memory to cache lots of vnodes in order > to be able to handle synchronizing scans without eating its disk alive. > -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0001150100540J.04098>