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 think you might rather go with parallelling it, maybe? Just having a fixed number of cpus for each, but using parallell (or something similar) to fire off several at the time.
----
George Marselis
Linux Engineer
HPC and Bioinformatics @NVI
________________________________
From: Karin Lagesen ***@***.***>
Sent: Wednesday, April 26, 2023 7:24:27 PM
To: NorwegianVeterinaryInstitute/DemultiplexRawSequenceData
Cc: Marselis, George; Assign
Subject: Re: [NorwegianVeterinaryInstitute/DemultiplexRawSequenceData] feature request: adjust fastqc -t switch according to the CPUs available in the system (Issue #55)
I think you might rather go with parallelling it, maybe? Just having a fixed number of cpus for each, but using parallell (or something similar) to fire off several at the time.
—
Reply to this email directly, view it on GitHub<#55 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASS7CRGEMOEH6SM44KDXCCDXDFK4XANCNFSM6AAAAAAXMTXMJQ>.
You are receiving this because you were assigned.Message ID: ***@***.***>
use lscpu | grep 'CPU(s):' | awk '{print $2 }' to find the amount of cpus
The text was updated successfully, but these errors were encountered: