MUX Export to CSV Job is very slow

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

MUX Export to CSV creates long running queries on the database that keep spinning for hour or longer and do not time out

STEPS TO REPRODUCE:

1. On a very large dataset go to Staff Grid in MUX
2. In view configure it so it shows 160k of rows and 3 different metrics in per period metrics
3. Export to CSV

Expected Results: The Export to CSV Job to take a reasonable amount of time

Actual Results: The SQL for the job runs on the database, executing each batch at a time, and Export to CSV Job may be running over 1 hour

Environment

All Supported Releases prior to 16.2.3

Resolution

This is DE81008, fixed in 16.2.3

Workaround:

1. Set CSV Export Job governor by running the command:
   admin governors -set ASYNC_E2CSV_MAX_ROWS 50000
2. Restart all services

Default value is 250000, if you experience performance issues, we recommend setting to 50k, or matching the Classic governor limit for CSV of 25k rows.

When the limit is hit:

If the user exports too many rows that are over the limit, they will see the below message in MUX after several seconds of running:

The Export to CSV Job will appear as Failed in Job Log and Job tables on the database level

Additional Information

Note: As best practice, encourage users to avoid exporting very large requests to CSV, i.e. hundreds of thousand of rows. Also avoid sending the same request simultaneously as this will affect performance