Sage X3: v12p36

Reference used:  Performance tuning your Sage X3 system: Print Server 

Note:

- This server also hosts web components of Syracuse and MongoDB. MongoDB service will always crash upon finding out no more memory (due to Sage X3 Print Server).

- RAM: 48 GB

- Maximum number of concurrent printing processes: 50 (non-negotiable; to account for peak printing period where waiting for print queue is not acceptable).

- There is consideration to move the Print Server to own dedicated instance as a final solution but there are on-premise infrastructure concerns.

During peak printing period, the Sage X3 website may randomly go down.

When my team did the postmortem on MongoDB:

```

{"t":{"$date":"(dateTime)"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"conn8","msg":"Writing fatal message","attr":{"message":"out of memory.\n"}}

```

Question:

- As temporary measure, is it advisable and how can I adjust the RAM usage of the Sage X3 Print Server service?