Just to clarify, we are not looking for metadata caching or refresh cache option (which is done after making config changes in the application)

Hi Martand,

eventually this is an problem of the start-up time for the OData Application Pool in IIS. It could be the case that the worker process first needs to start when the first request comes in and then it could take a moment until it’s up and running. You could try to change the App Pool setting to have it always running and not to be shut-down when idle.

Best regards
Roman

Thanks ​@roklde , OData App pool is already always running. There is no recycling setting in App pool. If the server is kept idle for sometime, again the next request coming after some interval it is slow, while subsequent requests are faster.

So, there should be some setting in the application that is sleeping automatically if no request is hitting the server for sometime and gets activated once a new request is coming (which is taking time), after the service is activated, other requests works fine.

Another thing that comes to my mind is the SESSION_TIMEOUT. It may that the token expires in the meantime and performing the login takes additional time:
 

Best regards
Roman