Date: Tue, 26 Feb 2013 08:22:05 +0200 From: Alexander Yerenkow <yerenkow@gmail.com> To: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au> Cc: freebsd-ports@freebsd.org, Aristedes Maniatis <ari@ish.com.au> Subject: Re: Share /var/cache/pkg/ between machines Message-ID: <CAPJF9wkeHqVzTZ7_Mzo7eYbPqcqs1khcap2SHw2a=sV5kwSJ2A@mail.gmail.com> In-Reply-To: <4749ABEC867549DAB07179A7E71CDB4F@white> References: <512C249B.4090401@ish.com.au> <4749ABEC867549DAB07179A7E71CDB4F@white>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't understand how do you imagine "magical appearing" 80 Mb JDK from any one place to other without pulling data from internet? :) In any case, with any kind of sharing you probably will have almost same traffic, maybe even greater than if you choose simple `pkg install` traffic. 1 - pointless, you can set up simple nginx, pointing to poudriere build packages directory and set up packagesite in /u/l/e/pkg.conf, without any proxy machine, which must download these cached packages in any case to be served by apache. AFAIK that machine will download something only while installing, right? So you overcomplicate your setup. 2. rsync will produce packagesize traffic + constant little more, due to checks of alteration. You'll lose in that case in long shot. My advice - put nginx to serve poudriere's built packages dir, and trust to xz compression level = easy to setup, not big traffic really. This is of course based on sentence "... onto 10 machines across the internet" - if you have some clusters with PCs in some nets, then you could think about rsync with primary poudriere, to serve locally packages for few other PCs. Hope this help :) -- Regards, Alexander Yerenkow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPJF9wkeHqVzTZ7_Mzo7eYbPqcqs1khcap2SHw2a=sV5kwSJ2A>