----- Original Message ----- > From: "Piotr Kliczewski" <[email protected]> > To: "Martin Betak" <[email protected]> > Cc: "[email protected]" <[email protected]>, "Eli Mesika" > <[email protected]>, "Martin Perina" > <[email protected]> > Sent: Wednesday, September 30, 2015 3:29:28 PM > Subject: Re: Doctor Rest PostgreSQL report > > 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.
Yes, right now I'm looking for other tools to provide me exactly with that. I just wanted to share the preliminary aggregated statistics. > > It would be good to understand implications of running doctor on the same > machine as engine and on other machine. > Indeed, this is precisely what I'm testing. The attached reports were with Doctor running on the same machine as the engine. > Thanks, > Piotr > > > On Wed, Sep 30, 2015 at 3:13 PM, Martin Betak <[email protected]> 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/ > _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
