Forum Discussion
OData performance issues
Thanks for reply, but unfortunatelly it's not helpfull at all.
I can use google myself and I already read those before I posted this question.
I'm looking for an answer to question why OData feed is much slower then downloading the data manually and using them as JSON source. Is it doing some validation against model which is time consuming or what?
Anyway even then the performance is terrible. Somebody with experience could tell if it's even worth a try to optimize this. Is our approach - download all and filter in Power BI, wrong for our data model? Is direct query - where we will filter data serverside based on user selected parameters better approach for this case?
Regards,
Michal
Hi,
Have you find an answer to the problem?
I have same issue with OData it is just terrible!
- Anonymous6 years agoNot applicable
Hi,
Unfortunatelly no.
PowerBI is not cappable of processing high-volume OData payloads effeciently. If your endpoint supports filtering and projections ($filter, $select), you can apply those operators by yourself and import result into PowerBI as plain JSON.
- Anonymous6 years agoNot applicable
Hi,
How do I know if my end poind supports that?
Can you please elaborate? Iam not well experienced in that part.
Your help is really really appreciated.Regards
- Anonymous6 years agoNot applicable
Look at the examples here:
https://www.odata.org/getting-started/basic-tutorial/#filter
https://www.odata.org/getting-started/basic-tutorial/#select
If it will work, then it's supported 🙂
Of course you have to adjust it to your data model.
If you don't know how your data model looks like, you can get single record with: ?$top=1 or you can check the /$metadata endpoint.