We are migrating from CData data sources to the TimeXtender REST API data source.
For Microsoft Graph API (used to retrieve calendars for multiple meeting rooms), the connection works correctly, but we are running into a major performance issue. While we retrieve the same amount of data.
Performance comparison:
Using CData:
- Ingest task: ~4 minutes
- Execute task per table: ~10 seconds
Using TimeXtender REST API data source:
- Ingest Full Load: 1.5 – 2 hours
- Execute task per table: 10–15 minutes
We have over 30 tables, so the execution time increases dramatically when using the TimeXtender REST API connector.
Question:
Are there any recommended ways to improve the performance of the TimeXtender REST API data source, both for the ingest phase and for execution runtime?
For example: configuration tips, concurrency settings, pagination options, or known limitations compared to CData?
Any guidance or best practices would be greatly appreciated.
