How to allow two reports to be processed simultaneously and in parallel?

[Gurpreet]

Hi,

When we load two reports in parallel  then any one report always stuck in loading and only load once one of them finish the loading. I even implemented the MSSqlserver cache but still the loading behavior is same. It seems Telerik reporting rest api always process one report request at a time and put other report request in queue. Can we make reports to load parallel?   

[Todor]

Hi Gurpreet,

Telerik Reporting REST Service renders reports in multiple threads in parallel. Each report is run in a new thread until the WorkerCount is reached. If the reports that should be rendered at the same time are more than the WorkerCount, some will be queued and their rendering will start in the first thread that becomes available.

Can you provide more details on the scenario so that we can think of the possible explanation for the observed behavior? Which version do you use? Do you use Custom Report Resolvers? Do you use any of our Viewers or the REST API in custom code?

Regards,
Todor
Progress Telerik

[Gurpreet]

Thank you for the reply.

This issue mainly occurs if we try to load  two large reports from  a separate  browser windows at a same time.

1. Reporting version -  12.2.18.1129 -  R3 2018 
2. Yes, Custom Report Resolver

  configurationInstance = new ReportServiceConfiguration
            {
                HostAppId = "Html5App",
                Storage = new MsSqlServerStorage(connectionString),
                ReportResolver = new CustomReportResolver(),
            };

     3. https://docs.telerik.com/reporting/html5-report-viewer (Viewer default to Print Preview Mode)

 

 

 

[Todor]

Hi Gurpreet,

I confirm that with version 12.2.18.1129 the reports are rendered in parallel, with a configurable count of threads. Is it possible that the REST Service is configured to use a single thread, for example, if it is running on a virtual machine?

You may attach a Trace Listener to the service. Our code writes relevant information in the trace log that may point us to the core of the issue.

Regards,
Todor
Progress Telerik