On 03/31/10 11:10 AM, William Schumann wrote:
Given the package list currently defaulting for the Automated Installer,
from a local mirror here in Prague, it took almost 14 minutes to finish
the image_create(), plan_install() and to count the sizes at the cost of
186MiB all in <image directory>/var/pkg/. The reported size was 2.8GiB,
which sounds approximately correct. Ran 2 trials on a Ultra 20.
Is there any way to accelerate this process in order to inform the user
sooner about size requirements? Can we avoid the var/pkg/ downloads?
image_create()?
I'm sure it could be, there are a few open RFEs:
385 fast access to size of packages in repo
4134 pkg operations should report operation sizes
With that said, there are a few things that would be helpful to know:
* how long does a second planning operation take after the first
one has completed?
* is this local mirror a pkg.depotd? does it have apache in front
of it?
One thing to keep in mind is that pkg.depotd doesn't currently compress
catalog or manifest data on the fly like a reverse Apache proxy can.
Using an Apache reverse proxy in front of your depot could significantly
reduce transfer time and the following RFE covers it:
9687 support for accept-encoding desired
Also note that all of the manifests that were downloaded to perform this
operation would have been retrieved anyway to perform the actual install.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
