Closed
Reporting Capacity in Pega Marketing
As part of a Pega Marketing campaign run, I am trying to extend the OOTB reporting capability with a couple of new reports to aid marketing simulations. The problem I am having is the amount of data being retrieved (upto 100k rows) and rendered on the screen (the reports have a number of aggregates). At these volumes, the report brings down the JVM (it does recover) after running out of memory (4GB heap). So my questions:
- What is the maximum number of rows that a report can handle with a heap size of 4GB?
- How can a trigger the direct export of the report to excel (real time, not scheduled) without running the report itself?
- Would the amount of data that just an export could handle be greater than running the report?
Posted: 9 years ago
PEGA
Pegasystems Inc.
US
Hi modhr1,
I don't have an exact figure based on rows, since the number of columns you are including and the data being exported plays a role in it. We don't have an exact maximum but I've done some testing in the past. With 50 columns and 25,000 records it consumed, at peak, around 1 gig of memory. I don't have the values of each column anymore but this will give you an idea.
Which version of PRPC are you on? have you had a look at the pxConvertResultsToCSV activity?
We don't progressively load the report so loading 100k rows in the dom would cause a lot of issues. I would suggest you make use of paging for this.