Thanks for the help. It worked out with the client setting= =C2=A0keepalive=3Dtrue.

Though curl is pre-enabled with keepalive=3Dtru= e. Below curl command worked out to avoid TLS handshake in subsequent=C2=A0= calls.

curl -k -H "X-Auth= -Token: $token" -H "Content-Type: application/json" -X GET h= ttps://${bmc}/redfish/v1/Systems/= system=C2=A0https://${bmc}/redfis= h/v1/Systems/system

Thanks,

Sharad

On Wed, 6 Oct 2021 a= t 00:23, Ed Tanous <edtanous@goog= le.com> wrote:

On Tue, Oct 5, 2021 at 11:48 AM John Broadbent <jebr@google.com> wrote:
>
>
>
> On Tue, Oct 5, 2021 at 1:42 AM sharad yadav <sharad.openbmc@gmail.com> wr= ote:
>>
>> Hi All,
>>
>> We have tried to measure redfish APIs performance benchmarking on = AST2600.
>> On redfish GET request there is a penalty added for ~100ms on TLS = handshake at

This is a little higher than I would've expected, but not outside the realm of reasonable.=C2=A0 Can you triage what cipher suite you're
negotiating between the client and server?=C2=A0 Are you using a DH+EC key<= br> cipher?=C2=A0 That should be faster than RSA.

>> https://github.c= om/openbmc/bmcweb/blob/master/http/http_connection.hpp#L297
>>
>> On trying below all methods, each request calls `async_handshake` = which adds 100ms delay
>> before the actual redfish handler code gets called.
>> Method 1:
>> curl --insecure -X POST -D headers.txt https://${bmc}/redfish/v1/S= essionService/Sessions -d=C2=A0 =C2=A0 '{"UserName":"roo= t", "Password":"0penBmc"}'
>> export token=3D<Read X-Auth-Token from the headers.txt>
>> curl -k -H "X-Auth-Token: $token" -H "Content-Type:= application/json" -X GET https://${bmc}/redfish/v1/Systems/system
>>
>> Method 2:
>> export token=3D`curl -k -H "Content-Type: application/json&qu= ot; -X POST https://${bmc}/login -d '{"username" : "root= ", "password" : "0penBmc"}' | grep token | awk= '{print $2;}' | tr -d '"'`
>> curl -k -H "X-Auth-Token: $token" -H "Content-Type:= application/json" -X GET https://${bmc}/redfish/v1/Systems/system
>>
>> Method 3:
>> curl https://${bmc}/redfish/v1/Systems/system --insecure -u root:0= penBmc -L
>>
>> We want to avoid this ~100ms delay for better performance.
>> Please suggest if there is a way to skip the `async_handshake` cal= l by modifying the requests method?
>>
>> Thanks,
>> Sharad
>
>
>
>
> There is logic in the crow::connection object that should allow you to= use tcp keep-alive and avoid the handshake in start.
> https://github.com/o= penbmc/bmcweb/blob/master/http/http_connection.hpp#L694
>
> I have looked at the connection class in bmcweb before, and found it d= ifficult to understand.
> However, this is a simplified version of the states within the connect= ion class:
>
> start->doReadHeaders->doRead->handle->completeRequest->= doWrite[if keep alive]->doReadHeaders
>
> The async_handshake is in the start, so if you are able to use the sam= e connection, you should only pay for the handshake once.
> Ed Tanous and Gunnar Mills are the definitive experts.

Yep, John got this exactly right.=C2=A0 Make sure whatever client you'r= e
using is taking advantage of keepalive, and you will only take this
TLS performance hit for the first request.

>
>
> Let us know what you find.
> Thank you

--000000000000a7404705ce14d536--