On 7/4/2025 8:26 AM, Markus Armbruster wrote:
Steve Sistare writes:
Using qom-list and qom-get to get all the nodes and property values in a
QOM tree can take multiple seconds because it requires 1000's of individual
QOM requests. Some managers fetch the entire tree or a large subset
of it wh
On 7/4/2025 8:33 AM, Markus Armbruster wrote:
Steve,
My sincere apologies for the long, long delay.
It wasn't just for the usual reasons. It was also because I had a vague
feeling of unease about qom-tree, and had trouble figuring out why.
I'll try do your work justice before the window for 1
Steve,
My sincere apologies for the long, long delay.
It wasn't just for the usual reasons. It was also because I had a vague
feeling of unease about qom-tree, and had trouble figuring out why.
I'll try do your work justice before the window for 10.1 closes.
QOM maintainers, please have a look
Steve Sistare writes:
> Using qom-list and qom-get to get all the nodes and property values in a
> QOM tree can take multiple seconds because it requires 1000's of individual
> QOM requests. Some managers fetch the entire tree or a large subset
> of it when starting a new VM, and this cost is a
Steve Sistare writes:
> Using qom-list and qom-get to get all the nodes and property values in a
> QOM tree can take multiple seconds because it requires 1000's of individual
> QOM requests. Some managers fetch the entire tree or a large subset
> of it when starting a new VM, and this cost is a
Using qom-list and qom-get to get all the nodes and property values in a
QOM tree can take multiple seconds because it requires 1000's of individual
QOM requests. Some managers fetch the entire tree or a large subset
of it when starting a new VM, and this cost is a substantial fraction of
start up
