blob: 2c691289908a1af4463d2eb732a60190b2ab0eac (
plain)
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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
<?xml version="1.0"?><!--*-nxml-*-->
<!DOCTYPE manpage SYSTEM "xmltoman.dtd">
<?xml-stylesheet type="text/xsl" href="xmltoman.xsl" ?>
<!--
This file is part of PipeWire.
-->
<manpage name="pw-profiler" section="1" desc="The PipeWire profiler">
<synopsis>
<cmd>pw-profiler [<arg>options</arg>]</cmd>
</synopsis>
<description>
<p>Start profiling a PipeWire instance.</p>
<p>If the server has the profiler module loaded, this program will
connect to it and log the profiler data. Profiler data contains
times and durations when processing nodes and devices started and
completed.
</p>
<p>
When this program is stopped, a set of gnuplot files and a script to generate
SVG files from the .plot files is generated, along with a .html file to
visualize the profiling results in a browser.
</p>
</description>
<options>
<option>
<p><opt>-r | --remote</opt><arg>=NAME</arg></p>
<optdesc><p>The name the remote instance to monitor. If left unspecified,
a connection is made to the default PipeWire instance.</p></optdesc>
</option>
<option>
<p><opt>-h | --help</opt></p>
<optdesc><p>Show help.</p></optdesc>
</option>
<option>
<p><opt>--version</opt></p>
<optdesc><p>Show version information.</p></optdesc>
</option>
<option>
<p><opt>-o | --output</opt><arg>=FILE</arg></p>
<optdesc><p>Profiler output name (default "profiler.log").</p></optdesc>
</option>
</options>
<section name="Authors">
<p>The PipeWire Developers <@PACKAGE_BUGREPORT@>; PipeWire is available from <url href="@PACKAGE_URL@"/></p>
</section>
<section name="See also">
<p>
<manref name="pipewire" section="1"/>,
</p>
</section>
</manpage>
|
