Problem with "-perf on" command

[HazemEldahshan]

Hi,

I want to know how to ensure that different statistics (I/O, Run, Solution, etc.) are written to the .out file. I tried adding -force on as an additional keyword to launch_mapdl, but it did not work.

Thanks

[germa89]

I would expect those statistics are alway written to the out file. Which one are you missing?

[HazemEldahshan]

They are written when the -perf command is used while creating a new MAPDL session. This works fine in Mechanical. In PyMAPDL, I added -perf on as an additional argument, but I could not find the statistics being written as expected.

[germa89]

@HazemEldahshan it does not seem it is a documented command:

https://ansyshelp.ansys.com/public/account/secured?returnurl=///Views/Secured/corp/v252/en/ans_ope/Hlp_G_OPE3_1.html

I would open a ticket with service support for getting more information about it.

[pmaroneh]

As a workaround, this code can provide some insights:

output = mapdl.solve()
run_stats = mapdl.run("/RUNSTAT") 
with open(os.path.join(os.getcwd(), "solver_stats.out"), "w") as f:
    f.write("Run Statistics\n")
    f.write("=" * 60 + "\n\n")
    f.write(str(run_stats))
    f.write("\n\n")

[HazemEldahshan]

Hi,

I tested this but still not all infornations can be found. For example, I want to know the time taken for form an assembly vs solve steps.

Best regards,
Hazem

[mikerife]

Hi @HazemEldahshan @germa89
Hazem the 'mode' of MAPDL that PyMAPDL launches is not batch or interactive, it is 'as a server'. Which is different than either batch or interactive. What I think is happening is that when MAPDL batch is normally exited the performance information is written to the output file. Whether by APDL /exit or /eof commands or the Mechanical style /wb,file,end. However the aaS instance has two main differences:

1 It is meant to be 'always on'. So we don't necessarily exit, rather we disconnect from the running instance.
2 The PyMAPDL version of 'exit' hard kills the MAPDL aaS process.

From 2 I think that means there is nothing to 'tell' MAPDL to print out the performance stats. If true then I think that would mean we would need a MAPDL enhancement request to add a user accessible method of dumping those performance stats on demand. @germa89 does this sound reasonable or am I way off?

In the mean time you could add the 'dspoption,,,,,,performance' command which will echo out some of the same information. Also the jobname.dsp or jobname.pcs files (depending on the solver type used) will also have some useful solution stats that may be of interest.

Mike

[HazemEldahshan]

Hi Mike,

Thanks for your detailed answer. The problem is that dspoption,,,,,,performance does not get all the output data that I want. Could you please tell me if the enhancement request has been already created?

Hazem

[mikerife]

HI @HazemEldahshan Yes, I created enhancement MECH-I-4893. If anyone reading this thread would like have their vote added please comment here and @ me and I'll add the vote.