Lines Matching refs:any

12 {any}`sec_ploginfo`, PETSc provides a mechanism for
14 {any}`sec_profbasic` introduces the various profiling
27   primary means of monitoring the performance of PETSc codes. See {any}`sec_ploginfo`
32   program’s performance. See {any}`sec_PetscInfo`
38 As discussed in {any}`sec_mpelogs`, additional profiling
45 As shown in {any}`listing <listing_exprof>` in {any}`sec_profiling_programs`, the
51 libraries, followed by any user-defined events (discussed in
52 {any}`sec_profileuser`). For each routine, the output data
58 one *flop* as one operation of any of the following types:
70 {any}`fig_library`. Each `KSP` solver is composed
79 {any}`listing <listing_exprof>`, which was generated by solving a
130 {any}`sec_nestedevents`.
137 within {any}`listing <listing_exparprof>` and {any}`listing <listing_exparprof2>`,
148 [datafiles](https://gitlab.com/petsc/datafiles), see {any}`petsc_repositories`.
150 The first {any}`listing <listing_exparprof>` presents an overall
155 {any}`sec_profstages`) are also given. Information about the
157 the second {any}`listing <listing_exparprof2>`). Finally, a summary of
214 the following {any}`listing <listing_exparprof2>`. The summary for each
302 total computation and to any user-defined stages (discussed in
303 {any}`sec_profstages`). These statistics can aid in
306 {any}`ch_performance` gives suggestions about achieving good
329 {any}`sec_deactivate`.
332 application as any MPI application, and follow the MPI implementation’s
362 Note that user-defined stages (see {any}`sec_profstages`) will be ignored when
398 {any}`sec_mpelogs`); one should see the manual page for
488 {any}`sec_profaccuracy`.
505 {any}`sec_profileuser`).
538 {any}`sec_matsparse`, `-info` activates the printing of
541 One can selectively turn off informative messages about any of the basic
600 discussed in {any}`sec_profileuser`, PETSc can automatically
625 {any}`sec_mpelogs`.)
637 of profiling described in {any}`sec_profstages`, we can
642 {any}`listing <listing_exparprof>` and {any}`listing <listing_exparprof2>`.
645 within event stages 5 and 6. {any}`sec_parperformance`
684 To view the data, start `nsys-ui` without any arguments and then `Import` the