Export to Excel (data only) performance hit when exporting large amounts of data using stock data providers and OBS security

Document ID : KB000020109
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Customers using Export to Excel (data only) to export large amounts of data via either OOTB or custom portlets built off our own data providers are running into java heap OOM errors. These customers all have in common (so far) are instance rights granted via OBS groups for the user running the export, and grid portlets using many columns and many rows. The OOM condition can be triggered by either running concurrent large exports (so far seen with 10k or more), single large exports approximately 100k or more and by executing an export request waiting and then triggering the request to run again and again by hitting the browser back button and starting the request over again.

We currently do not recommend customers use any Export to Excel from a grid portlet as a reporting replacement. However, we do not prevent this so therefore we have many large customers who have relied upon these grids in 8.x and before as reports who are now upgrading to 12.1.x and experiencing performance issues. We also warn customers not to use the back button... but we don't prevent that either. Customers upgrading from 8.x to 12.1.x are now running into memory starvation issues after upgrade as the queries to produce the export now produce a larger file upon output and tap into our data provider security.

Steps to Reproduce:

  1. On a dataset with a very large amount of customer data, create a grid portlet based upon one of our stock data providers (resource for example) - or you can use resource workloads as an example
  2. Add columns showing a variety of details or use the stock columns
  3. Login as a user who has instance rights to various resources project instances granted via OBS groups
  4. Either filter or show all insuring you have a large number of results in the output (10k or more)
  5. Export to Excel
  6. Do this same steps in a system pre-12.0.5 and SQL trace it - compare results

Expected Result: Export to Excel to remain close to the same performance wise pre-12.1
Actual Result: Export to Excel time has increased

 

Solution:

WORKAROUND: 

Use global security, reduce the number of rows to export (lower limit), reduce or limit columns depending upon data, increase hardware to allow for more system resources

STATUS/RESOLUTION:

CLRT-64628
Resolved in Clarity 13.1.0 Generic Patch. Reference TEC581256
Resolved in Clarity 13.2.0 Generic Patch. Reference TEC599354
Resolved in Clarity 13.3