Skip to main content
To homepage To homepage
Question

REST API datasource much slower then Cdata source

  • February 23, 2026
  • 3 replies
  • 61 views
M
Explorer

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.

    3 replies

    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • February 24, 2026

    Hi ​@Mies 

    What version of the data source provider and TimeXtender are you experiencing this on?

    How do you run the data source on a schedule?

    I would like you to isolate one large endpoint/rsd file and look at how many rows are transferred and how long it takes.

    M
    Explorer
    • Mies
    • Author
    • Explorer
    • February 25, 2026

    Hi ​@Thomas Lind ,

    We are using the TimeXtender REST Data Source version 12.1.0.0 and TimeXtender Data Integration version 7257.1.

    I created a copy of the data connector in the portal so I could re-run just one of the endpoints. I noticed that this copy executed very quickly. I then tested the copied data connector by running all endpoints, and it still completed relatively fast, around 10 minutes.

    This made me curious, because it is the exact same data connection. So I edited the original data source in TimeXtender Data Integration and changed the connection to point to the copied data connector I created in the portal. After doing that, the execution time became extremely long again (still running after 45 minutes and not even half of the endpoints are executed).

    This suggests that the data source in TimeXtender Data Integration might be corrupted or behaving unexpectedly. I’m not sure how this could have happened, but I assume the issue will be resolved if I use the new data source. Unfortunately, this will require a lot of remapping work, which I was hoping to avoid, but it appears to be the only way to fix the problem.

    Do you have any idea what might have caused this issue in the data source, and how we can prevent it from happening again in the future?

     

     

    Thomas Lind
    Community Manager
    Forum|alt.badge.img+5
    • Thomas Lind
    • Community Manager
    • March 11, 2026

    Hi ​@Mies 

    Thanks for doing this. So it seems like it wasn’t specifically the provider that is slow, but something else.

    I would like to make an Zendesk ticket for this.

    Terms and ConditionsCookie settingsAccessibility statement