Reporting out of memory | Community
Skip to main content
CIGM
CIGM
Level 3
October 30, 2017
Solved

Reporting out of memory

  • October 30, 2017
  • 5 replies
  • 4942 views

Hi there,

Can you please tell me how can I fix the following error that's popping out when I try to run a bespoke online report?

Any help would be great.

Thanks,

cc

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jean-Serge_Biro

Hi Carlotal,

First of all, you should indeed follow Adhiyan's advice:

increasing Javascript from 64MB to 512MB is almost mandatory for custom and complex reports on large tables.

In parallel, you should try to optimize the report queries: most of time, it is a question of too much complex groups in the page activity/list table, and often resolved by doing some groups/count by in the Query activity instead.

Alternative, when this is not a question of count/group by but more a question of lines count : restricting result set to a medium value, if possible for you.

But of course, it depends on each use case.
So please may you share more information about your page report/underlying SQL query?

Hope this helps.

Regards
J-Serge

5 replies

Adhiyan
Adobe Employee
AdhiyanAdobe Employee
Adobe Employee
October 30, 2017

Hello There,

Increase the memory defined in the Javascript section of the serverconf.xml file.

The javascript maxMB should be increased and followed by nlserver config -reload and you should be good to go.

<!-- Configuring the JavaScript interpreter

         maxMB :  Maximum size in megabytes before running the garbage collector Default: 64

         stackSizeKB :  Size of each stack chunk in kilo octets Default: 8 -->

    <javaScript maxMB="64" stackSizeKB="8"/>

Regards,

Adhiyan

CIGM
CIGMAuthor
Level 3
October 30, 2017

Hi there,

Thanks for this but is there an easy way to do this by just selecting it in the query?

Thanks,

cc

Jean-Serge_Biro
Jean-Serge_BiroAccepted solution
Level 10
October 30, 2017

Hi Carlotal,

First of all, you should indeed follow Adhiyan's advice:

increasing Javascript from 64MB to 512MB is almost mandatory for custom and complex reports on large tables.

In parallel, you should try to optimize the report queries: most of time, it is a question of too much complex groups in the page activity/list table, and often resolved by doing some groups/count by in the Query activity instead.

Alternative, when this is not a question of count/group by but more a question of lines count : restricting result set to a medium value, if possible for you.

But of course, it depends on each use case.
So please may you share more information about your page report/underlying SQL query?

Hope this helps.

Regards
J-Serge

badr_eddinez
badr_eddinez
Level 2
August 29, 2018

Hii

I've the same problem "OUT OF MEMORY" in the reports sections, i wanted to try the solution of increasing the MAXMB from 64 to 512 but i cant edit the serverconf.xml file.

Im asking if there is other solution or a way to have access to edit the xml file.

Thanks.

A
Adobe Employee
anshshar_cfsAdobe Employee
Adobe Employee
August 29, 2018

Hi Badr

If your instance is on premise, only then you would be able to access the serverconf.xml file.

However, in case it is a Adobe Hosted Solution , then you would need to file a support request from the support portal to have support staff to look into your request.

Regards

Anshul Sharma

Terms & ConditionsAccessibility statement

Loading footer...