Learning Forum

[rprichard]

I've recently discovered the benchmarking command:(benchmark '(physical-time-steps ))nThis outputs three numbers:cortex CPU time, solver CPU time, and elapsed time. I've found that the last item is real-world time taken by the benchmark, but I can't quite put my finger on the significance of the first two. Solver CPU time is approximately equal to elapsed time multiplied by number of threads, and cortex time seems to represent time taken by overhead, such as I/O operations. nWhile the command is still useful, it isn't very confidence inspiring to just have guesses as to what the outputs mean. I'd also like to know if there are other possible inputs I'm missing.nCan someone point me to more formal documentation on the benchmark command? n

[Karthik R]

Hello,nI can provide some information about estimating these times. nYou could use this command but the below will give you more accurate results.n/parallel/timer/usagenThe above command includes only the solver time and to print Linear solver stats etc.. It doesn't include time spent in collecting, and reporting residuals, time spent in calculating and reporting monitors like (force, surface and volume). For measuring wall-clock time the below command should be used.n (benchmark '(iterate 200))nPlease see if these work. nHere is what I'd rely on. Please see the following links below from the User's guide.nI hope this helps.nThank you.nKarthikn