Dear Andrew,
Thanks for the response.
Sorry. When I said job.py I meant any "normal" firedrake script. When I run my job on my mac using just python it does run in serial and I have tested that I can use mpirun to run it in parallel. This is what I expected. It is on my ubuntu machine
that it seems to take up 32 cores even though I just used python, not mpirun. I wonder whether it might be using threads instead of cores?
I have not tried mpirun on this machine yet but I can easily do that. I am curious to better learn how efficient the parallelization is so I plan to do tests for different numbers of cores.
Best regards,
Francis
------------------
Francis Poulin
Associate Professor
Department of Applied Mathematics
University of Waterloo
email: fpoulin@uwaterloo.ca
Web: https://uwaterloo.ca/poulin-research-group/
Telephone: +1 519 888 4567 x32637
From: firedrake-bounces@imperial.ac.uk [firedrake-bounces@imperial.ac.uk] on behalf of Andrew McRae [A.T.T.McRae@bath.ac.uk]
Sent: Tuesday, April 26, 2016 6:25 AM
To: firedrake@imperial.ac.uk
Subject: Re: [firedrake] parallelization
Dear Francis,
What is job.py? If it is a "normal" firedrake script then approach 1) will not be running in parallel. If it is a python script that executes "mpirun -n 16 python simulation.py", on the other hand...
Best,
Andrew