[maker-devel] Hyperthreading

Carson Holt carsonhh at gmail.com
Tue May 23 14:38:42 MDT 2017


Also make sure cpus in the control file are set to 1 when using MPI. Otherwise it will tell each program it calls to try and use more CPUs per call.

—Carson

> On May 23, 2017, at 2:31 PM, admin at genome.arizona.edu wrote:
> 
> Carson Holt wrote on 05/23/2017 01:19 PM:
>> You can pull back to 128 would if you find that you are running low on RAM or have a high IO burden (both of which will double if you go from 128 to 256 even though CPU isn’t really doubling). Also MAKER per job performance plateaus at around 200 processes due to communication overhead. Above that threshold it is often useful to divide datasets into multiple separate jobs that can run simultaneously.
> 
> Yes, with '-n 192' we found the load on the cluster will initially go up to 360-380 but then continually decreases until maker is finished. Memory usage was very low during the processing (under 20%).
> 
> _______________________________________________
> maker-devel mailing list
> maker-devel at box290.bluehost.com
> http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org





More information about the maker-devel mailing list