When any user hits print on a report with more than 1000 results, the web server Memory will spike between 60-80% for a single print. If multiple users do this, it brings the Application Pool down.
This is caused by a known defect with the print feature. This has been ongoing since 5.x, but is difficult to resolve in the Archer code as this feature relies on a third party. The feature continues to be reviewed by RSA product management for improvement.
As a workaround, the PRINT option can be manually disabled in access roles that do not need to utilize this feature (export will still be available).
The attached script was provided by engineering to disable PRINT for all access roles in an instance. This script is to be used as-is; once these roles are updated the only option for rolling back the changes will be a database restore or manually change the access roles through UI.