File: profiling.htm

package info (click to toggle)
petsc 2.1.3-1.woody.1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 70,272 kB
  • ctags: 310,869
  • sloc: ansic: 257,275; sh: 9,870; makefile: 7,622; fortran: 6,211; cpp: 1,026; python: 416; csh: 41; asm: 9
file content (25 lines) | stat: -rw-r--r-- 1,207 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<html>
<title>profiling</title><body bgcolor="FFFFFF">
<h2>profiling</h2>
<menu>
<LI><A HREF="../../../src/sys/examples/tutorials/ex3.c.html"><CONCEPT>user-defined event</CONCEPT></A>
<menu>
Augmenting PETSc profiling by add events.<BR>Run this program with one of the<BR>
following options to generate logging information:  -log, -log_summary,<BR>
-log_all.  The PETSc routines automatically log event times and flops,<BR>
so this monitoring is intended solely for users to employ in application<BR>
codes.  Note that the code must be compiled with the flag -DPETSC_USE_LOG<BR>
(the default) to activate logging.<BR>
</menu>
<LI><A HREF="../../../src/sys/examples/tutorials/ex3.c.html"><CONCEPT>activating/deactivating events</CONCEPT></A>
<menu>
Augmenting PETSc profiling by add events.<BR>Run this program with one of the<BR>
following options to generate logging information:  -log, -log_summary,<BR>
-log_all.  The PETSc routines automatically log event times and flops,<BR>
so this monitoring is intended solely for users to employ in application<BR>
codes.  Note that the code must be compiled with the flag -DPETSC_USE_LOG<BR>
(the default) to activate logging.<BR>
</menu>
</menu>
</body>
</html>