Hello,
I couldn't find an answer here until now. But maybe there is a solution now.
For example, if I have 24 cores ( 48 virtual ) and i run a single simulation on windows with "fds_local -p 24 - o 1 XXX.fds" it works fine.
Defined in the .fds file: "&MESH ID='1' IJK=... MPI_PROCESS=0( .. 1 .. 23) /"
so, 24 differnet meshes and each assigned 1 core. ( works faster than with - o 2 ).
But if i want to run for example 2 simulations at the same time, each with 12 meshes and 12 cores i cant get a satisfying result as the computation time will increase (1 Simulation, 24 Mpi processes will finish in 3h and 2 simulations running at the same time, each of them needs 7h40min.)
--- starting the first simulation with "fds_local -p 12 - o 1 XXX.fds"
--- Defined in the .fds file: "&MESH ID='1' IJK=... MPI_PROCESS=0( .. 1 .. 11) /"
--- checking the Windoes Task manager / resource manager there is action in almost all 48 cores.
--- starting the second simulation with "fds_local -p 12 - o 1 XXX.fds"
--- Defined in the .fds file: "&MESH ID='1' IJK=... MPI_PROCESS=0( .. 1 .. 11) /"
(As the definition of the MPI processes needs to start at 0 again)
--- checking the Windoes Task manager / resource manager there is action in almost all 48 cores. but 2 of them running at about 100% (CPU 26 and 30) and another 2 running at almost 0% (CPU 27 and 31) all the other CPUs vary over time between 100% and 0%
(The cells for each mesh are almost the same)
Maybe the 2 running at 100% do slow down the simulation time.
Is there any solution to fix this on windows ?
if not, is there a way to make this work on linux ? Or should i keep going with 24 meshes / cores in 1 simulation.
Thanks