Open EricR86 opened 8 years ago
Original comment by Michael Hoffman (Bitbucket: hoffman, GitHub: michaelmhoffman).
@ericr86 Can you please document this in Genomedata? I don't think there needs to be an option to set this within Genomedata. Client programs can change directly using the tables
interface if they need to.
segway-task
should also set both of these to one since there is an assumption that one Segway task = one thread. I don't think any other part of Segway or Segtools should be modified, for now. Then you can close this.
Original comment by Michael Hoffman (Bitbucket: hoffman, GitHub: michaelmhoffman).
Many people will be in an environment where they assume one thread per process unless they do something to change it. And they might violate, say, a cluster use policy to declare the number of threads or cores being used, if they aren't made aware of this.
Original report (archived issue) by Coby Viner (Bitbucket: cviner2, GitHub: cviner).
PyTables defaults to using 4 threads. This could pose a problem for cluster usage and could also be made more efficient when more slots are available.
It may be worthwhile for Genomedata to override the default values of
tables.parameters.MAX_NUMEXPR_THREADS
andtables.parameters.MAX_BLOSC_THREADS
.If not, this behaviour is likely something that Genomedata should explicitly document.