Performance Issue in Lodata Discovery

[AHolzerSCT]

Hello,

I am struggling with the performance of Lodata Discovery.
In my LodataServiceProvider I discovering for all the requests starting with the lodata.prefix around 300 Models (with a lot of relationships between them).
Even though I set the LODATA_DISCOVERY_TTL = null (so forever) on my local pc, with local db a very simple select * from a table with 3 records takes around 2 seconds.

Am I missing something in the configuration?

If I remove all the Models from the Discovery (except the one I am selecting) the same request takes around 100ms.

Thank you in advance

[Remo]

Does this help #868?

[AHolzerSCT]

So far I was able to do only a quick test and the result seems quite promising! Using file based caching on my development PC it improved response time from 1.5 - 2 seconds to 0.4 - 0.5 seconds.
Not quite yet the times of a custom API without ODATA discovery (which takes for the same data around 0.05 seconds on my pc), but still a good improvement.

[Remo]

Thanks for the feedback! I currently have 60 entities and it takes me 90ms. Not knowing the hardware difference between us, if we take my 90ms and adjust it because you have more models, we get 450ms which would be exactly where you are. I guess we still have a linear performance degradation with every entity we have. With caching I would hope this wouldn't happen. I'll be on vacation soon, it's going to take some times, but I'll try to look into it.

[AHolzerSCT]

Any plans when this can be merged?