Xporter needs a lot of time to export 200 records

[Santiago Estel]

Xporter is currently taking more than 50 minutes to export 900+ records.

This is not acceptable for our end users.

Our server has four CPUs, 24 GB RAM and Jira is set to use 8GB as max heap memory.

While doing another test exporting 200 records, Xporter needed 3 minutes to complete the task and the server did not show any sign of stress.

Any idea of how to improve this performance? Or this a normal performance?

[Nic Brough -Adaptavist-]

I'm afraid exporting issues is a complex and involved process, which means it is resource intensive and with large data sets, it is using a lot of memory, probably causing the server to need to use swap space, which is a very slow thing to have to do.

Taking a long time to do a large data set is normal.  Although I'd probably want to check if there were other resource intensive processes running at the same time, which also might slow it down.

[Santiago Estel]

I found that removing two Xporter Insight iterative items from the report makes Xporter to render the file in seconds.

It seems that this issue is because these two items are build for each ticket on the report.

I'll take another look tomorrow, and see if something can be adjusted.