On 2013-16-09 6:22, Luke Kanies wrote:
On Sep 15, 2013, at 8:55 PM, Henrik Lindberg <henrik.lindb...@cloudsmith.com>
wrote:
On 2013-16-09 5:41, Luke Kanies wrote:
Hi Henrik,
I know we have some users who just batch all package installs up front. It'd
be interesting to see if that was a feasible solution. it would by pass the
graph entirely, which I'm sure could have problems, but it would, at least, be
easy to build and understand. Would that suffice for a sufficient number of
cases?
Well, it naturally misses the optimization opportunity and is obviously
difficult to maintain for users since they then have to compose the set of
packages manually without the help of the graph / catalog.
They don't have to compose the set of packages; we'd provide a hook that pulled
all of the packages out of the catalog and ran them in a batch.
That would certainly optimize the package operations.
There are tricky issues with ordering though, sometimes batching is not
possible unless user has prepared the exact set of things to give to the
package manager. And it may need to go back and forth between different
types of packages - do other things in between etc.
I'm not sure which optimization you mean, though.
That it currently deals with packages one by one and that can be very
slow depending on the package manager compared to giving it several
package operations at once.
- henrik
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-dev.
For more options, visit https://groups.google.com/groups/opt_out.
