<div dir="ltr"><div><div><div><div><div>Martin,<br><br></div>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.<br></div>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.<br><br></div>It would be good to understand implications of running doctor on the same machine as engine and on other machine.<br><br></div>Thanks,<br></div>Piotr<br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 3:13 PM, Martin Betak <span dir="ltr"><<a href="mailto:mbetak@redhat.com" target="_blank">mbetak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
I performed a stress test using FakeVDSM environment with 200+ hosts<br>
and 500+ VMs.<br>
<br>
Attached are generated HTML reports for this environment.<br>
In both cases I tried to simulate some random load using existing<br>
webadmin. In the '_doctor' case the simple connector from [1] was<br>
running *in addition to* the legacy UI.<br>
<br>
The used pgCluu tool [2] which may be useful<br>
for DB experts for some further insight.<br>
<br>
I wanted to send this out as soon as possible so we can better analyze<br>
our current performance and the possible impact Doctor Rest<br>
integration would have on the system.<br>
<br>
Please feel free to review the attached reports and/or suggest other<br>
ways/tools how to better benchmark the DB load caused by Doctor Rest.<br>
<br>
Thank you very much.<br>
<br>
Best regards<br>
<br>
Martin<br>
<br>
[1] <a href="https://gerrit.ovirt.org/#/c/45233/" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/45233/</a><br>
[2] <a href="http://pgcluu.darold.net/" rel="noreferrer" target="_blank">http://pgcluu.darold.net/</a></blockquote></div><br></div>