Setting the OMP_NUM_THREADS environment variable to 1 will make it use only 1 core.
Tim On Sat, Jun 6, 2015 at 4:43 AM, Daniel P. Bliss <[email protected]> wrote: > Hi HCP Users, > > There appear to be commands within PostFreeSurferPipelineBatch that use > multi-threading, because my call to this script was just terminated due to > its over-use of resources on our computing cluster. Termination occurred > at one of the calls to wb_command -- within CreateRibbon, I believe, > probably the first call in that script. None of the wb_command calls > contain any obvious multi-threading flags. > > Does wb_command use multi-threading by default? If so, how can I turn it > off? > > For what it's worth, here's the output of a call to "top" just before the > process terminated: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 6264 dbliss 20 0 1988m 324m 9988 R 2140.2 0.4 2:33.03 wb_command > 29044 dbliss 20 0 563m 123m 17m R 99.8 0.1 21:59.53 python > 29072 dbliss 20 0 563m 122m 17m R 99.8 0.1 21:57.55 python > > Note that wb_command is using 2000+% of the CPU resources. > > Many thanks, > Dan > > _______________________________________________ > HCP-Users mailing list > [email protected] > http://lists.humanconnectome.org/mailman/listinfo/hcp-users > _______________________________________________ HCP-Users mailing list [email protected] http://lists.humanconnectome.org/mailman/listinfo/hcp-users
