Nicolas Williams wrote: > On Wed, Sep 05, 2007 at 01:55:32PM -0700, John Forte wrote: > >> We're not using svccfg, so no. We have a project specific cli and >> library for our clients. The SMF property groups and properties will >> likely be project private (assuming that is possible). svccfg and/or >> libscf will not be the preferred tools to update this project's >> configuration repository. >> >> The performance won't be an issue for normal day-to-day use. It will >> only be a factor if a customer wanted to preload a configuration for >> this project. I just wanted to ensure that what I was seeing was "normal". >> > > I don't know enough about the libscf API, but if I understand correctly > that it does not talk to svc.configd for pg updates until the > transaction is committed, then you should be able to batch all your > updates into one transaction (or a small number of them). That should > go a lot faster than one transaction per-prop update. > Since we're providing a library and CLI that do not have batch semantics, I cannot do that. If need be, for a "load configuration" scenario, we'll provide special operations. But I doubt it will be required from a customer perspective. As I said, I just want to ensure that what I was seeing was expected.
- John
