On Mar 9, 2005, at 9:09 PM, Ricky Tang Siu Hong wrote:
> Hello,
>
> Our cluster nodes has 2 SMP CPU and with hyperthreading giving 4 CPU.
> But linux scheduler always switch the CPU of LAM process, causing
> decreasing of performance (HPL result cut half).
>
> So we use "taskset" utility to start LAM process. This is done by
> using schema:
> n0 -np 1 taskset 1 ./xhpl
> n0 -np 1 taskset 8 ./xhpl
> n1 -np 1 taskset 1 ./xhpl
> n1 -np 1 taskset 8 ./xhpl
> ...
>
> This works, but have some inconvenience. To change the CPU used by
> the job, we need to change the schema file too. This goes agaist that
> when we use PBS TM startup, everything is specified through parameters
> of qsub (no need to change mpiexec line in job script).
>
> Is there a smarter way to use taskset in LAM startup? Or is there an
> option to set affinity in LAM internally?
I don't know if there is a smarter way to use taskset - I'm not at all
familiar with the command, as I don't usually deal with hyperthreading
(and tend to believe that it causes more problems than it solves right
now with Linux). Perhaps someone on the list has some useful
experience they would like to share?
I can tell you that there is no affinity setting support in LAM, and it
is unlikely such support will be added in the near future.
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have an LAM/MPI day: http://www.lam-mpi.org/
|
