I’m experiencing a performance issue with the OData endpoint in Acumatica. After an app pool recycle or idle period, the very first call to an OData resource takes a noticeably long time, then subsequent calls are much faster. I wanted to post here to check if this is expected behaviour, and gather tips on how to reduce this delay
Environment:
Acumatica version: Build 25.101.0153
IIS app pool: default settings
Database on same server/SQL Server 2019
No customizations affecting INLocation OData endpoint (basic table, exposed via DAC)
First call in postman:

And second call:

Is it expected that the first OData call after idle is significantly slower?
Are there recommended best practices (warm-up scripts, Application Initialization in IIS, etc) specifically for the OData endpoint?