REST BAQ call is quite slow?

Epicor ERP 10
1

I’m calling a relatively simple BAQ via REST API and it’s taking consistently 3 seconds to return results.

image
image.png1578×562 42.7 KB

The same query in the BAQ editor returns results much faster:
image
image.png1193×810 42.7 KB

Any idea why this performance difference?
I have noticed it with certain other simple queries as well, whereas if I call one that returns thousands of rows and 5 columns, it executes in like .7 seconds? very odd

2

Is tehre a lot of content? Maybe the parsing / serializing to JSON is consuming the time?

3

Not really, it’s only returning like 5-12 columns and only a few rows

4

Read this

2 Likes
5

Sounds like because it’s a baq, the model is not cached and has to be regenerated for each call, which is why it takes longer for REST rather than the designer, where it may be cached?

1 Like
6

Upgrade to 10.2.200.14 or greater. This was addressed in that release

2 Likes
7

I’m on 10.2.200.3, so that would help to explain it :slight_smile:

8

NO, cache is not implemented yet, but probably BAQ part work faster in the latest release.

9

Sounds like I need to actually make the effort to upgrade then :slight_smile: Thanks Olga!

10

@Aaron_Moreng what tool is that in your first screenshot?

11

Hey jeff that’s a screenshot from postman

12

Ah ok. Have you tried executing the rest call locally in your environment and throwing a stopwatch on it?

13

Ain’t nobody got time for that :wink: jk but it’s essentially running locally against the server so it’s not going out over the internet or anything. Sounds like it’s fixed in a higher version than I have

14

I’m still on 10.2.100.8. Is that likely why CustomerSvc.GetByID takes a whopping 15 seconds to return one row?

15

CustomerSvc.GetByID is not a BAQ call, so the issue discussed before is not applicable. For services model is cached on the first call after application pool started and then reused.

3 Likes