You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 12, 2024. It is now read-only.
Is your feature request related to a problem? Please describe.
Currently we can only set a hard value for memory when submitting ACDC or autoACDC. If we are doing autoACDC for those 50660 WFs from different campaign with different maxPSS, setting it to a same value for all those WFs won't be promising to fix the issue.
Describe the solution you'd like
Instead of setting the memory to a hard value, we can set it to a relative value, like assigning a 25% or 50% increase based on the original maxPSS. This would work for all 50660 WFs with different maxPSS settings.
Describe alternatives you've considered
None
The text was updated successfully, but these errors were encountered:
Impact of the new feature
autoACDC
Is your feature request related to a problem? Please describe.
Currently we can only set a hard value for memory when submitting ACDC or autoACDC. If we are doing autoACDC for those 50660 WFs from different campaign with different maxPSS, setting it to a same value for all those WFs won't be promising to fix the issue.
Describe the solution you'd like
Instead of setting the memory to a hard value, we can set it to a relative value, like assigning a 25% or 50% increase based on the original maxPSS. This would work for all 50660 WFs with different maxPSS settings.
Describe alternatives you've considered
None
The text was updated successfully, but these errors were encountered: