Dear Yann,
On 30/04/2018 13:31, Yann Sagon wrote:
Dear Kenneth,
2018-04-30 11:32 GMT+02:00 Kenneth Hoste <[email protected]
<mailto:[email protected]>>:
Dear Yann,
On 30/04/2018 11:28, Yann Sagon wrote:
> I just noticed that building TF17 with cuda compute 6.0 and 6.1 doesn't
> respect the job-cores = 12 that I have in my config file. According to
> htop, it's using ~28 cores
Did you submit the TF build as a job using "eb --job"?
The --job-cores configuration setting only applies to build jobs
submitted using --job.
duhhh! Sorry about that, I'm dumb. Indeed I should use the parallel flag
in my case.
But to be honest, I don't see why there are two different flag for
almost the same purpose?
They're not exactly the same purpose, but the difference is subtle.
Maybe a good example that combines both helps:
eb --job --job=cores=J --parallel=P ...
This will make EasyBuild submit a job using J cores, to build something
using (exactly) P cores.
With P<J, this may make sense when the build requires a lot of memory
for example.
The default value for --parallel is to use as many cores as there are
available, so assuming the job requests J cores, --parallel=J is the
default when no other value is specified for --parallel.
More or less at least, since there are other factors that come into play
like "ulimit" settings which may restrict then number of cores used by
default, and an easyconfig file can override the --parallel setting
(default or not) with for example 'parallel=1' or 'maxparallel=2'.
regards,
Kenneth
