Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Multi-threading use of cores #322
Less of an issue, more of a plea for consideration before implementing the proposed new feature of 'greedy' core usage.
The trouble is that we don't always have the rights to use all the cores on the machine that we are using. If I am running cutadapt in a shared HPC environment, I emphatically do NOT want it to use all the cores that the OS reports. I want it to use just as many as I have told it that it can use. If my 4 core job suddenly decides that it can use all 40 cores on the node that it has been allocated to, then there are a large number of other users going to be cross that they are now contending for cores with my badly-behaved process. I would strongly argue that the default behaviour should be single core, with an option to specify
Hi, and thanks for the feedback! Yes, you’re absolutely right that the behavior of using all existing cores would be bad. My idea was to use the number of available cores. Some cluster systems use the
I would really like for cutadapt to have sane defaults, and using all available cores would be one of them, but I can see that this might a problem on a system wher