-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
everything is single threaded now? #911
Comments
Can we close this now that #912 has been merged? |
Yes, similar to the other PR, I think @notestaff 's description of PR #912 needed to say "fixes" or "closes" #911 before it merged, in order for merging to close this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When executing command line viral-ngs in google cloud, either within a conda environment on a manually created VM, or within dsub/PAPIv2, I'm noticing that
--threads 1
is being passed to pretty much every subprocess call.I note two possible bugs here:
cfs_period_us
instead ofcfs_quota_us
?cfs_quota_us
is reporting-1
, perhaps using that value to denote unlimited quota. This meansavailable_cpu_count()
is always reporting1
instead of the number of processors available on the machine. This line should change to treat-1
as infinity.The text was updated successfully, but these errors were encountered: