there are a couple of different approaches that you can take to prevent this issue from happening. As you rightly said, revising the configuration of the FastSort component is one of these options that goes right to the bottom of the problem. However, the configuration is quite complex in terms of balancing the sorting speed and the memory consumption of this component. Another option that eliminates the need for a complex configuration is to replace FastSort with the ExtSort
component. As a matter of fact, ExtSort is what we generally recommend in similar situations (overconsumption of the heap memory by FastSort) and what also proves to work in most cases.
Given the known facts, I would advise you against setting up arrangements on the server level without sorting out the core of the problem (on the component level). Nevertheless, if you would like to discuss this issue in more detail I would suggest logging a support ticket via our CloverCARE Customer Portal
as we would need to dig deeper into the details of your use case.