I have given the run in cluster in Code Saturne 7.2
The run is in progress for hours and the listing file is not getting updated or saving any data in RESU folder
When I end kill the listing file, getting the following message
No "partition_input/domain_number_800" file available
Kindly help me
No "partition_input/domain_number_800" file available
Forum rules
Please read the forum usage recommendations before posting.
Please read the forum usage recommendations before posting.
-
- Posts: 35
- Joined: Thu May 19, 2022 4:37 pm
-
- Posts: 4206
- Joined: Mon Feb 20, 2012 3:25 pm
Re: No "partition_input/domain_number_800" file available
Hello,
Do you have a backtrace when you kill the job ?
Which partitiong option are you using ?
Regrds,
Yvan
Do you have a backtrace when you kill the job ?
Which partitiong option are you using ?
Regrds,
Yvan
-
- Posts: 35
- Joined: Thu May 19, 2022 4:37 pm
Re: No "partition_input/domain_number_800" file available
"Pt-Scotch" was used for partitioning. The error was trace in the Idris cluster. The support team gave the following information.
"MPI processes run on the same core. This is the reason why the performance is bad."
Sofen
"MPI processes run on the same core. This is the reason why the performance is bad."
Sofen
-
- Posts: 4206
- Joined: Mon Feb 20, 2012 3:25 pm
Re: No "partition_input/domain_number_800" file available
Hello,
I have had reports of a job placement issue on one of the IDRIS clusters, but have not had feedback yet on my last exchange (the install is very similar to one of an older version without those issues, bit with a slightly different environment).
Aligned the install (compilers, prerequisites, ...) on the "normally working" version would be a good start. Differences/prerequisite updates could then be installed one by one, so as to find out what is causing an issue in that install.
Best regards,
Yvan
I have had reports of a job placement issue on one of the IDRIS clusters, but have not had feedback yet on my last exchange (the install is very similar to one of an older version without those issues, bit with a slightly different environment).
Aligned the install (compilers, prerequisites, ...) on the "normally working" version would be a good start. Differences/prerequisite updates could then be installed one by one, so as to find out what is causing an issue in that install.
Best regards,
Yvan