Run Time Data-Binding: Performance

Posted by: katie.koslosky on 14 September 2021, 3:01 am EST

  • Posted 14 September 2021, 3:01 am EST

    We are using run time data binding as described here (a necessity based on the fact that we are using cookies for authorization and traditional data binding does not seem to allow that)

    The performance is slow on large data sets (I'm working with about 25,000 rows currently). Is that a consequence of using run-time data binding? Will using an endpoint as a datasource be faster because the entire data string is not stored in the report object?

    And important question - I see Major Release v3.0 is supposed to include support for large data sets of more than 100,000 records. Will that help in the runtime data binding case? Or only when defining endpoints as datasources?
  • Replied 20 September 2021, 7:31 pm EST

    I am not sure what's the problem with cookies? If a server-side of your app sends headers to tell the browser to store cookies, then the browser should automatically send back previously-stored cookies to the server using the Cookie header. Does not it work?
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels