Hi Shawn,
On 01/11/10 05:39 PM, Shawn Walker wrote: > On 01/11/10 09:41 AM, Fr?d?ric VANNIERE wrote: >>> Another thing that might be contributing to this is how AI is >>> performing the installs. >>> Can you provide the full install log? >> >> It's here : http://pastebin.com/m3c26ca80 >> >> Note: The PWKinstall-opensolaris package is downloaded from a custom >> IPS repository and is post-install my customization script (I'll post >> about this latter) . > > That helps quite a bit; AI appears to be executing the pkg command to > install each package separately and for other tasks (over 90 times). Yep - that is how AI currently installs packages listed in AI manifest. > > That's going to be much slower than simply executing the pkg(1) > command once for all packages to be installed. Not only that, AI > should really be using the python pkg.client.api that's provided > instead as that would further reduce the overhead of the operations it > is performing. That is interesting - thank you for pointing this out. Do you happen to have more data about what the difference is with respect to the overhead of particular approaches you mentioned: * calling pkg(1) for each package * calling pkg(1) for all packages at once * consuming directly pkg.client.api We are mostly interested in memory consumption as well as well time execution. As far as stability of those APIs is concerned, are there any significant differences between pkg(1) and pkg.client.api ? I mean if we switch to pkg.client.api, should we assume to be hit by API changes more often than we currently are with pkg(1) ? Also, pkg(1) man page is useful source of information and often used as API documentation, is pkg.client.api API documented somewhere as well ? Thank you, Jan
