Searched refs:timing (Results 1 – 9 of 9) sorted by relevance
291 …timing=$(touch timing.out && grep -E '(user|sys)' timing.out | awk '{if( sum1 == "" || $2 > sum1 )…292 printf "time %s\n" "$timing" >> "$logfile"
407 # To get timing results run configure #687 - **Problem too large for physical memory size**: When timing a696 the timing results are essentially meaningless.697 - **Overhead of timing routines on certain machines**: On certain699 slow; this skews all of the flop rates and timing results. The file
24 The bandwidth is then computed as `3*n*sizeof(double)/min(time[])`. The timing is done with `MPI_Wt…
832 is too large, or for timing.
228 timing results, it is *crucial* to read this information.
567 for testing or convergence studies, not for timing. These `KSPSolve()` monitors may
60 - Add new option to `-log_view` to view nested event timing
1111 To see the full timing information for the five most expensive tests use
1358 Outputs a comprehensive timing, memory consumption, and communications digest