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
I've noticed that when I have a module like an evaluation module that does something very quick like subtracting two numbers, DSC tends to hang up or fail. The two most common things that I see are an error message that a job was killed or DSC just stopping and hanging until I kill it with no error message.
In the configuration file, I have tried setting the small modules to run with 100 or 500 instances per job to reduce the amount of jobs. I got more errors when I increased this to 1000 (these were mostly errors saying that a job had been killed).
Is there something I can do to improve this? I've currently modified my pipeline so that each analysis step also does the simple evaluation step but this isn't ideal because it requires lots of copying code.
Thanks!
Jean
The text was updated successfully, but these errors were encountered:
@jean997 indeed something simple but concrete would help. After you increase it to 1000 instances per job, how many jobs in total do you still end up having? I would expect less errors when you increase it for per job ... We would like to review your other configurations and I can try on my end too if we have a simpler example.
I've noticed that when I have a module like an evaluation module that does something very quick like subtracting two numbers, DSC tends to hang up or fail. The two most common things that I see are an error message that a job was killed or DSC just stopping and hanging until I kill it with no error message.
In the configuration file, I have tried setting the small modules to run with 100 or 500 instances per job to reduce the amount of jobs. I got more errors when I increased this to 1000 (these were mostly errors saying that a job had been killed).
Is there something I can do to improve this? I've currently modified my pipeline so that each analysis step also does the simple evaluation step but this isn't ideal because it requires lots of copying code.
Thanks!
Jean
The text was updated successfully, but these errors were encountered: