Facing time delay when send a first request to call Eikon Data API?

priyanka

Hi,

I noticed that if I send a 1st request (with API key), it takes a bit longer than when I send a subsequent request. I presume there is some delay in authentication initially. In order to improve user experience, should I send a dummy request maybe when a user starts filling inputs so that their requests are processed a bit faster?

Please provide the suggested way?

Thank You,

Priya

zoya faberov

Hello @priyanka,

Personally, I would not send any dummy requests for the purpose of speed up or to improve user experience.

The session is initiated once, then multiple requests are issued.

The user knows when they have started the app, so it is not unexpected for them.

Different requests also can take unequal amount of time, so this will not guarantee all requests very quick.

Plus this request will count toward EIKON DATA API USAGE AND LIMITS so if, for some reason, the user decides to rapidly restart the app repeatedly, dummy requests can potentially be generated on every restart and that can lead to hitting limits, which would be obviously undesirable.

Depending on what you run and what you observe, it may be additionally useful to test, if the startup of Eikon session from Eikon Data API is the only initialization happening and contributing to the perceived delay. Sometimes environments, such as Jupiter notebook, also introduce some additional overhead, so running "naked" python command line may be a clean test, and may allow you to better understand the full nature of the delay.