Yikes, none of those response times are reasonable... For comparison, what is the ping response times for your system?
And to try to reduce the number of variables, are you using Basic Auth or a Redfish Session for all of these? I want to make sure we're not getting "session creation / teardown" mixed in the comparisons.
For a clear first test, can you just try an unauthenticated GET on /redfish/v1 (the Service Root) and compare those results?
All of those times should be a small fraction of what you are seeing...
Thank you for the response, yes YIKES, those times are horrible and that is an issue that has to and is being worked. All of these should use Basic Auth, (just getting into Redfish so many questions) A basic Auth does not create a session? The python script is as follows BMC_IP="https://10.8.1.90" LOGIN="Administrator" PASSWRD="xxxxxxxx"
I know the Redfish Python library will perform a few requests up front to probe the service:
redfish.redfish_client( ... ): This will perform a GET on /redfish/v1 to locate the sessions URI
REDFISHOBJ.login(): This will interact with the session collection by either performing a POST to create a new session, or GET to sanity check the credentials for Basic Auth
So, in your sample script, it will perform three HTTP operations total; two for the construction and login using the Redfish library, and one for the GET operation you're performing. I assume that 8 seconds is the end-to-end completion of your Python script and not the individual call with "REDFISHOBJ.get"? If so, it makes sense why there's a discrepancy with curl and Postman.