Skip to main content
Solved

First OData call takes long time for /api/odata endpoint

  • October 20, 2025
  • 3 replies
  • 68 views

yurakova
Freshman I

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)


Example
GET http://<server>/AcumaticaERP/t/Company/api/odata/dac/INLocation?$select=LocationID,SiteID,LocationCD,Descr

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?

Best answer by Dmitrii Naumov

Both UI and API are noticeably slower when accessed the first time after app restart. 

The reason is that the app needs to build caches first, and that takes a lot of time. 

3 replies

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • Answer
  • October 20, 2025

Both UI and API are noticeably slower when accessed the first time after app restart. 

The reason is that the app needs to build caches first, and that takes a lot of time. 


yurakova
Freshman I
  • Author
  • Freshman I
  • October 20, 2025

@Dmitrii Naumov 
Got it, thanks for clarifying!

So there’s no built-in way to avoid the initial delay - the only option is to periodically ping the site or specific endpoints (like /Main or /api/odata/$metadata) to keep the caches?


Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • October 20, 2025

@yurakova correct.