Redfish on OpenBMC

[Rapkiewicz, Pawel]

Hi Chris, Yugi,

Thanks for your benchmarking you've attached, I'd like to better understand the data. I'm curious about 10 concurrent requests for redfish root service. The average is ~5 seconds for uwsgi, and mostly no response for gevent.
Few questions:
- gevent and uwsgi, those are two independent redfish server implementations?
- do you have any traffic during retrieving root service?
- Was it with Basic HTTP Auth, or without any?

I'm also little confused on how do we measure and present code size and performance, since it's not normalized anyhow, it's biased by the measurement method. If the intent of gathering those data is to
compare different Redfish approaches, we shall consider setting the measure criteria. Some suggestions:

Code size:
- real code size, not on compressed file system
- is it binary or script?
- what's the size of dependent libraries (already existing in OpenBMC environment vs. the new one required only by given Redfish implementation)?

Performance:
- We need common script for measurement
- And common method, I'd prefer running on machine directly connected to the OpenBMC platform to minimize network latency, or to run it over loopback interface on the platform, but this may affect context switching
- The performance will still be biased by the CPU the Redfish is running, but it will be closer to make it comparable.

Regards,
Pawel


-----Original Message-----
From: openbmc [mailto:openbmc-bounces+pawel.rapkiewicz=intel.com at lists.ozlabs.org] On Behalf Of Chris Ong
Sent: Wednesday, February 7, 2018 5:15 PM
To: Tanous, Ed <ed.tanous at intel.com>; Yugi Mani <yupalani at microsoft.com>; Ali Larijani <alirhas at microsoft.com>; Paul.Vancil at dell.com; hramasub at in.ibm.com; Michael.E.Brown at dell.com
Cc: rolfb at us.ibm.com; jwcarman at us.ibm.com; openbmc at lists.ozlabs.org; pradeep.kumar36 at tcs.com; bradleyb at fuzziesquirrel.com; Balaji.B.Rao at dell.com
Subject: RE: Redfish on OpenBMC

Hi Ed,

On our AST2520 platform:
Reading sensors using Redfish takes about 12-13 seconds for about 200 sensors. If 10 threads are requesting the read at the same time, the average time to return is about 70 seconds.

For reading logs, it takes about 100 seconds for 4000 log entries. The time scales linearly with the number of logs, e.g. for 2000 logs, it would take around 50s.

Chris

-----Original Message-----
From: Tanous, Ed <ed.tanous at intel.com>
Sent: Wednesday, February 7, 2018 8:09 AM
To: Yugi Mani <yupalani at microsoft.com>; Ali Larijani <alirhas at microsoft.com>; Paul.Vancil at dell.com; hramasub at in.ibm.com; Michael.E.Brown at dell.com
Cc: Balaji.B.Rao at dell.com; bradleyb at fuzziesquirrel.com; jwcarman at us.ibm.com; openbmc at lists.ozlabs.org; pradeep.kumar36 at tcs.com; rolfb at us.ibm.com; Chris Ong <Chris.Ong at microsoft.com>
Subject: RE: Redfish on OpenBMC

> > Performance
> > How fast is it?
> Synchronous API for Sensors and SEL takes longer to respond.
> It takes about 19 seconds for 100 sensors and more than 6 minutes for
> 4000 events.
> 10 concurrent requests can make them 4-5 times slower than usual.
> Asynchronous API for BMC and component firmware update takes 5-10 
> minutes as expected.
> These results are on AST2400.

Do you have the same data for your 2500 platforms?

--------------------------------------------------------------------

Intel Technology Poland sp. z o.o.
ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.

Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek
przegladanie lub rozpowszechnianie jest zabronione.
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by
others is strictly prohibited.