We've moved!
This site is now read-only. You can find our new documentation site and support forum for posting questions here.
Be sure to read our welcome blog!

SplitNCigarReads uses more than 1 core with no options to set number of cores used

If running on a cluster system that kills jobs if they use more than their allocation, you need to be able to either know how many cores are required or be able to limit the number of cores used. Are there options I am missing? Otherwise I would like to know the recommended number of cores to request for this tool. Is the number of cores used based on what the machine has? If so that needs to be limited for a cluster or cloud system. Right now I am requesting 4 cores per job but the jobs spend most of their time at < 200% CPU usage.


Sign In or Register to comment.