[Chetan Patel]

Hello all,

I am facing the problem to run the converge with utilisation of core. We have windows operating system with Intel (R) Xeon (R) CPU E5-2683 V4 @ 210 GHZ with 2 sockets, cores-32 and logic processors-64. I give the command initially "converge-2.4.18-msmpi-win64 super" as well as "converge-2.4.18-serial-win64 super". Converge start simulations with the 3% utilisation of CPU.
So, I tried commands like "mpiexec -n 32 converge-2.4.18-msmpi-win64 super" or "mpiexec -n 32 converge-2.4.18-msmpi-win64 super.exe" etc.But, I am not able to start the smulations with those commands.

I am requesting you to give me suggestions to improve the CPU utilization with inclusion of available cores and logic processors.

Thank you.

[KapilO8]

Originally Posted by Chetan Patel

Hello all,

I am facing the problem to run the converge with utilisation of core. We have windows operating system with Intel (R) Xeon (R) CPU E5-2683 V4 @ 210 GHZ with 2 sockets, cores-32 and logic processors-64. I give the command initially "converge-2.4.18-msmpi-win64 super" as well as "converge-2.4.18-serial-win64 super". Converge start simulations with the 3% utilisation of CPU.
So, I tried commands like "mpiexec -n 32 converge-2.4.18-msmpi-win64 super" or "mpiexec -n 32 converge-2.4.18-msmpi-win64 super.exe" etc.But, I am not able to start the smulations with those commands.

I am requesting you to give me suggestions to improve the CPU utilization with inclusion of available cores and logic processors.

Thank you.

Hey,

Check if the solver executable name is correctly typed and present in system path or in the working directory with license file. Also the mpi command would be mpiexec.exe followed by the no of processors and the converge executable.

For 18 cores and converge executable name with converge-msmpi.exe, That would be

mpiexec.exe -n 18 converge-msmpi.exe

[Chetan Patel]

Dear Kapil,

Thank you so much for your immediate reply. I am still facing difficulty to run the case in parallel mode. I gave a command "mpiexec.exe -n 32 converge-2.4.18-msmpi-win64.exe super"(I need to add 'super' keyword as we have superbase licence). I received an error "failed to post close command error 1717" and "unable to tear down job tree".
However, I succeed to start the simulations with "mpiexec.exe -n 32 converge-2.4.18-serial-win64.exe super" with 23% CPU utilization and 36% memory utilization.
I want to use te maximum capacity of my Processor. Any suggestions to improve the simulation speed will be appreciated.
Thanks.

[JPovich]

HI Chetan,

Do you have Hyperthreading enabled on your system? This setting is found in the BIOS screen. You generally want this feature disabled for any HPC software. In my experience, hyper-threading causes major performance issues on Windows systems for HPC programs.

You can check if it's on by seeing if Windows thinks there are 32 or 64 cores.

[Chetan Patel]

Originally Posted by JPovich

HI Chetan,

Do you have Hyperthreading enabled on your system? This setting is found in the BIOS screen. You generally want this feature disabled for any HPC software. In my experience, hyper-threading causes major performance issues on Windows systems for HPC programs.

You can check if it's on by seeing if Windows thinks there are 32 or 64 cores.

Hi JPovich,

Thank you so much for your reply. I will disable hyperthreading.

With Regards,
Chetan

[KapilO8]

Curious to know, whats a superbase license?

[JPovich]

Superbase license doesn't limit the core count of your job.

For a single job, traditional licenses use 1 "converge" license and N-1 "converge_child" licenses where N is the number of ranks in your job.

For a single job, a superbase run just checks out 1 "super" license. That's it. Whether you run a 32 core job or a 4096 core job, it still only checks out one "super" license.

[KapilO8]

Oh.. That's new to me.. Thanks for the info JPovich

By the way, did disabling hyperthreading worked Chetan?

[Chetan Patel]

Originally Posted by KapilO8

Oh.. That's new to me.. Thanks for the info JPovich

By the way, did disabling hyperthreading worked Chetan?

Hi Kapil,
I am still facing the issue with running converge in parallel mode. I contacted converge support and they pointing towards some issue with the supporting software.

This system worked well in parallel mode by using same command before 2 months when operated by another person . So, I need to recheck again the supporting softwares.

It is very strange that I am able to run successfully in serial mode but not in parallel mode.
Any way, May I know which organiation you working?
Thanks,
With Regards,
Chetan

[Chetan Patel]

Originally Posted by JPovich

Superbase license doesn't limit the core count of your job.

For a single job, traditional licenses use 1 "converge" license and N-1 "converge_child" licenses where N is the number of ranks in your job.

For a single job, a superbase run just checks out 1 "super" license. That's it. Whether you run a 32 core job or a 4096 core job, it still only checks out one "super" license.

Thanks Jpovich for this information. As, I am also not aware of it.