Question #244277 on Yade changed: https://answers.launchpad.net/yade/+question/244277
Klaus Thoeni posted a new comment: Ok, it seems that we should try to by Intel then ;-) And here some more testing on my local machine with yade-batch and one single simulation. @ Bruno: note the influence of affinity. Btw, the IT guy told me that on a "smart" grid affinity is usually set automatically but this might not be the case on your desktop. Here we go, two tests each: $ yade-batch -j1 file.py: 00:02:12 $ yade-batch -j1 file.py: 00:02:14 $ yade-batch -j2 file.py: 00:02:14, cpu 100% $ yade-batch -j2 file.py: 00:02:16, cpu 100% $ yade-batch -j2 --cpu-affinity file.py: 00:02:16, cpu 100% $ yade-batch -j2 --cpu-affinity file.py: 00:02:17, cpu 100% ...so far so good since --job-threads is not defined $ yade-batch -j2 --job-threads=2 file.py: 00:02:13, cpu 200% $ yade-batch -j2 --job-threads=2 file.py: 00:02:13, cpu 200% ...computer tells me is uses 2cpus but simulation time is still the same $ yade-batch -j2 --job-threads=2 --cpu-affinity file.py: 00:01:58, cpu ~140% $ yade-batch -j2 --job-threads=2 --cpu-affinity file.py: 00:01:34, cpu ~140% ... interesting, setting --cpu-affinity seams to help, although using 1.4 cpus only $ yade-batch -j3 --job-threads=3 file.py: 00:02:00, cpu ~150% $ yade-batch -j3 --job-threads=3 file.py: 00:02:03, cpu ~150% $ yade-batch -j3 --job-threads=3 --cpu-affinity file.py: 00:02:04, cpu ~150% $ yade-batch -j3 --job-threads=3 --cpu-affinity file.py: 00:02:03, cpu ~150% ... no improvement here. -- You received this question notification because you are a member of yade-users, which is an answer contact for Yade. _______________________________________________ Mailing list: https://launchpad.net/~yade-users Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
