Closed stemangiola closed 4 years ago
Currently Makeflow does not support that, but I have opened this issue:
https://github.com/cooperative-computing-lab/cctools/issues/2366
Hello @stemangiola - I want to make sure we clearly understand your use case before we write any code. Is your goal to put an upper limit on the run-time of each task, because some of them may hang indefinitely? Or is there something else going on?
Hello, often setting accurate walltime can favor backfill of jobs around bigger jobs. Different steps in the workflow might need different walltimes. Setting up a general walltime is not the best thing.
Ok, so the point here is that you want that walltime conveyed to the scheduler, and not that you have a desire to kill the job after a certain point, right?
(Although the scheduler might end up doing that if you exceed the walltime.)
On Thu, Aug 20, 2020 at 10:23 AM Stefano Mangiola notifications@github.com wrote:
Hello, often setting accurate walltime can favor backfill of jobs around bigger jobs. Different steps in the workflow might need different walltimes. Setting up a general walltime is not the best thing.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cooperative-computing-lab/makeflow-examples/issues/35#issuecomment-677696963, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVADESNSQU6S3XYCBMVY63SBUWUVANCNFSM4QFTTIBQ .
Yes,
I would like setting wall-time in the same way I set CPU or MEMORY.
Sounds good, I should have a pr shortly.
Hello, thanks for makeflow.
I have a script like the one below. What should I use insteal of
TIME=xxx
for custom walltimes (I'm using slurm)?Thank a lot!