yade-users team mailing list archive

[Jérôme Duriez <question252455@xxxxxxxxxxxxxxxxxxxxx>]

New question #252455 on Yade:
https://answers.launchpad.net/yade/+question/252455

Hi,

Let's say I launch two yade-batch instances (in two different terminals..), each with --cpu-affinity. Apparently all batch executions will send jobs to cores starting from the "first" one, leading to slower execution.

Example: Let's say I have 4 cores: "cA", "cB", "cC", "cD" (corresponding to 1,2,3,4 lines in htop)
I launch:
"batch A (containing 2 jobs)" :  yade-batch --job-threads 1 --jobs 2 --cpu-affinity
"batch B (containing 2 jobs)" :  yade-batch --job-threads 1 --jobs 2 --cpu-affinity

>From what what I observe, apparently both "job 0" from batchs A and B will run on the same core cA. Whereas the best behaviour would be that
job 0 batch A -> core cA          job 1 batch A -> core cB
job 0 batch B -> core cC          job 1 batch B -> core cD

Is it possible to define this, in the batch table ? I did not find in the doc. Thanks,

Jérôme

-- 
You received this question notification because you are a member of
yade-users, which is an answer contact for Yade.