I would try to look while the execution on the taskmanager and afterwards on the load-logfile and the governance-dashboard to find the reasons - here is a very new tip to them: What is New Row Applicator ?
But I think you will need to make some optimizing efforts.
I haven't done any adjustments or testings to this topic by myself but I think to change this setting within the settings.ini won't improve the performance else it will be only hide these message.
Therefore if you haven't a real performance problem you could ignore it and if there are performance issues you should look at load-statements and consider a split of them in more specific parts and/or smaller slices. This meant to separate such steps like filtering, aggregation and joining data into own loadings and put whose results together - you will have more (factor 2-3) more loadings put the overall performance is often significantely better. Similar effects occur often if you sliced data-transformations maybe on year-level and concatenate them afterwards again.
Thank you for your comment. Changing the settings.ini file as was suggested will not hide the concerned message in the logfile. That was my point.
We have some performance issues on our two frontend servers running QVS. And we very often see this error message (warning) in the event logs, just before a server crash due to lack of memory. Each server is equipped with 256 GB RAM, but this issue still is occurring!
I would try to look while the execution on the taskmanager and afterwards on the load-logfile and the governance-dashboard to find the reasons - here is a very new tip to them: What is New Row Applicator ?
But I think you will need to make some optimizing efforts.
