Lines Matching refs:program

25   program’s conclusion. These statistics are comprehensive and concise
32   program’s performance. See {any}`sec_PetscInfo`
35   `-info`, is useful to see where a program is hanging without
47 output or an ASCII file at the conclusion of a program. See `PetscLogView()` for all the possible
139 output generated by the `-log_view` option. The program that generated
143 and then solves the resulting linear system; the program then repeats
431 global flop counter for the entire program.
439 within a program. One can independently monitor several "stages" of code
456 stages within an program.
477 `-log_view` for a program that employs several profiling stages. In
478 particular, this program is subdivided into six stages: loading a matrix and right-hand-side vector…
537 algorithms and tuning program performance. For example, as discussed in
618 paging by the operating system. Generally, when running a program, only
628 program, we have found an effective procedure is to run the *exact same
639 technique in the program
661 can be used to easily convert a regular PETSc program to one that uses
731 Next, run your program with TAU. For instance, to profile `ex56`,