Question
Evoke Technologies
IN
Last activity: 23 Feb 2018 6:53 EST
Report Definition running for too long and stops responding.
Hi,
I am having a Report Definition with a single class join. Records in both the data classes are around 20000. When i try to run the report, it runs for too long and stops responding. webpage throws some HTTP:504 error(Please refer the attached screenshot of the error). I assume this is due to huge data that needs to be fetched. But, i need an extract of this data. some one help me with this.
Thanks,
Bhargav.
-
Likes (1)
Gowtham Ganta -
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
IN
Hi Bhargav,
I somehow cannot really see the attached screenshot, can you please re-attach the same.
20000 records is not really too much of data, can you please be more specific about the SQL and the requirement.
We might have to evaluate the join conditions, wrong join can cost a lot on the SQL performance.
Thanks,
Sai
Pegasystems Inc.
US
Along with my colleague suggestion, kindly make sure that you don't have any un-optimized properties being used in the report, which might also cause the performance delay.
Evoke Technologies
IN
Hi Mahesh,
Thanks for the reply. There are no unoptimized properties that are included in the report.
Thanks,
Bhargav
Evoke Technologies
IN
Hi Sai,
Sorry, i missed attaching the file.
I am joining with a class using a single join condition in order to include one column from the joined class into the main report. It is actually simple join condition.
NOTE:I just tried running the report definition without any join condition, but still i got the same error. so, this might have not occured due to incorrect join condition.
Please find the attached document for applied join condition and error screenshots.
Thanks,
Bhargav
Pegasystems Inc.
IN
Thanks for the reply Bhargav.
That error is very abstract and we really cannot get anything out of it.
Its just a gateway time out.
On the joins, please understand that removing the joins won't help, adding proper joins will help to filter unnecessary data. (in the context of inner join)
But I see that according to your requirement, there is just this 1 join condition that can help. Please see if there are any other columns on which we can add joins, or are we sure if we added all the filter criteria that is needed under the where clause ?
Can you please extract the SQL from the tracer and run it directly on the SQL client to see how long is it running ?
Can you please evaluate the PegaRules and Alerts log to see if there are any entries because of this query ?
Thanks,
Sai
Evoke Technologies
IN
Hi Sai,
I have verified PegaRules & Alert logs and there were no entries when filtered by the UserName.(As, i have run the Report Definition from the designer studio).
Does Running the extracted SQL directly on SQL Client means using "Connect-SQL" and calling it from RDB methods in an activity and trace it using DBTrace?
Thanks,
Bhargav
Evoke Technologies
IN
I could take the extract by running the SQL query directly from Connect-SQL and export the results to excel. But, unable to fetch the extract from the Report Definition.
IKOR
AU
If you think it's due to large sum of data , you could try limiting the max records to a smaller number and check it's working. Then you'll know what to address.
Evoke Technologies
IN
Hi Kasun,
Thanks for the response. I tried limiting the max number of records to 500 and it worked fetching the records.
Regards,
Bhargav