-C n Specify the number of child images to update in parallel. When recursing into child images (usually zones), update at most n child images in parallel. The default number of child images to update in parallel is 1. If n is 0 or a negative number, all child images are updated in parallel. See also PKG_CONCURRENCY in the "Environment Variables" section.... PKG_CONCURRENCY The number of child images to update in parallel. Ignored if the -C option is specified. When recursing into child images (usually zones), update at most $PKG_CONCURRENCY child images in parallel. If $PKG_CONCURRENCY is 0 or a negative number, all child images are updated in parallel. Default value: 1
I wonder if in the first paragraph (describing -C) or under PKG_CONCURRENCY if there should be some guidance on the impact of setting a value != 1. Although it's difficult to generalize this, I think the obvious concerns are around the memory usage during the plan creation (based on the -C value plus the # of packages installed) as well as the amount of I/O that will be queued up. Plus I don't know how well this would scale on the non-T4 sun4v based system. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
