Resolution:
deleteInvocationData, which is located in the Service Type Registry for each of your services. This determines when Service invocation status data on the Task Admin page is purged from the Admin interface. This data is stored in memory on the Broker, so this setting may need to be modified depending on how the service will be used. If you have this set to SERVICE_REMOVED, it will consume a lot of memory. SERVICE_REMOVED is not recommended as you can use the reporting database to see old statistics. Most customers that have manager memory issues have at least one service set to SERVICE_REMOVED. Additionally, if you have long running or shared services, you should set the value to INVOCATION_COMPLETED.

DDT (Direct Data Transfer) - You should have DDT enabled on both the driver and the engines so the service input and output data does not have to travel through the manager taking up memory and I/O resources. DDT for the driver is either set programmatically or in the driver.properties file. DDT for an engine is set in the engine configuration on the manager.