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 had a toil-wdl-runner use over 8G of memory in the leader Slurm job (and its local workers) and I had Slurm OOM-kill a child process of the leader that was running a WDLArrayBindingsJob.
We should make sure that we aren't somehow throwing around very large Python objects in the WDL interpreter. We might want to use MiniWDL's own JSON serialization where possible, somehow.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1641
The text was updated successfully, but these errors were encountered:
I had a toil-wdl-runner use over 8G of memory in the leader Slurm job (and its local workers) and I had Slurm OOM-kill a child process of the leader that was running a
WDLArrayBindingsJob
.This was running something like:
We should make sure that we aren't somehow throwing around very large Python objects in the WDL interpreter. We might want to use MiniWDL's own JSON serialization where possible, somehow.
┆Issue is synchronized with this Jira Story
┆Issue Number: TOIL-1641
The text was updated successfully, but these errors were encountered: