@LinaresToine before you dive too much with this development, I wanted to say that this is a delicate and intrusive change in Request Manager.

Having the ability to update a Merge task resource requirement would ideally require knowledge of the task name (e.g. DataProcessingMergeNANOEDMAODoutput, which means knowledge of the parent task name and the output module), which is not kept at the request JSON description. So it's a complex issue to solve and easy to make mistakes and inject new bugs. If we decide to follow this route, then we need to be well covered with unit tests as well.

About the TaskMemory new parameter that you propose, that would be very confusing, as Memory is already a task-level parameter. I'd rather explore other options here.

Thank you @amaltaro for your illustration. I agree that this development is quite intrusive. Perhaps its better to include new functions, rather than modifying existing ones for the time being. For example, the task types that are being ignored could have their own setMaxPSS function. In any case, Ill think of a way to make it as less intrusive as possible. One idea that comes to mind is finding a way to define the Memory parameter as a dictionary with taskNames from the T0 side, as this is already supported by the agent. Ill follow up on this. Thanks again

After discussing this issue with @amaltaro and @germanfgv , we have agreed to keep the memory value for merge tasks hardcoded in addRuntimeMonitors. The only change to make would be to change the 2.3 to 3.0. I'll update the patch accordingly.

For further record, this decision was made making this value configurable requires a lot of effort for something that rarely changes.

#12227 has been opened. It follows what was discussed last week.

@amaltaro.