Martin,

For me it would be great to understand how cpu, memory changes over time for the engine. I would like to see the same for doctor service.

I was not able to find it but it would be great to understand how many queries there were for both tests and how log it took to run them.

It would be good to understand implications of running doctor on the same machine as engine and on other machine.

Thanks,

Piotr

On Wed, Sep 30, 2015 at 3:13 PM, Martin Betak <mbetak@redhat.com> wrote:

Hi All,

I performed a stress test using FakeVDSM environment with 200+ hosts
and 500+ VMs.

Attached are generated HTML reports for this environment.
In both cases I tried to simulate some random load using existing
webadmin. In the '_doctor' case the simple connector from [1] was
running *in addition to* the legacy UI.

The used pgCluu tool [2] which may be useful
for DB experts for some further insight.

I wanted to send this out as soon as possible so we can better analyze
our current performance and the possible impact Doctor Rest
integration would have on the system.

Please feel free to review the attached reports and/or suggest other
ways/tools how to better benchmark the DB load caused by Doctor Rest.

Thank you very much.

Best regards

Martin

[1] https://gerrit.ovirt.org/#/c/45233/
[2] http://pgcluu.darold.net/