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
The scheduler gives unnecessary warnings when trying to assign tasks to processors. Also, the print format on these warning messages needs to be cleaned up.
Simple repro on Frontera:
Once the GPU memory fills up, the scheduler warns that the rest of the tasks may not be able to be scheduled even though they definitely can once previous tasks complete.
It may be worthwhile to have two separate warnings: one that warns that a task can't be scheduled right now due to lack of resources, and a separate warning for when a task won't ever be able to be scheduled (e.g. because it requires a GPU and more memory than any GPU has due to the memory argument in spawn).
The text was updated successfully, but these errors were encountered:
@arthurp@insertinterestingnamehere Is this something either of you would be able to take care of quickly, even if it's just a hack for me to disable the warnings on my end? I've got valid test cases that are printing the warning thousands of times and I'm concerned it's affecting my timing, so I need at least a temporary fix.
The scheduler gives unnecessary warnings when trying to assign tasks to processors. Also, the print format on these warning messages needs to be cleaned up.
Simple repro on Frontera:
Once the GPU memory fills up, the scheduler warns that the rest of the tasks may not be able to be scheduled even though they definitely can once previous tasks complete.
It may be worthwhile to have two separate warnings: one that warns that a task can't be scheduled right now due to lack of resources, and a separate warning for when a task won't ever be able to be scheduled (e.g. because it requires a GPU and more memory than any GPU has due to the
memory
argument inspawn
).The text was updated successfully, but these errors were encountered: