Skip to content

Commit f6d0383

Browse files
kartbennashif
authored andcommitted
samples: net: http_server: use proper language in code-block
Achieve proper syntax highlighting using "console" language when command snippets start with a prompt. Signed-off-by: Benjamin Cabé <[email protected]>
1 parent bd73073 commit f6d0383

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

samples/net/sockets/http_server/README.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ CPU Usage Profiling
103103
We can use ``perf`` to collect statistics about the CPU usage of our server
104104
running in native_sim board with the ``stat`` command:
105105

106-
.. code-block:: bash
106+
.. code-block:: console
107107
108108
$ sudo perf stat -p <pid_of_server>
109109
@@ -117,14 +117,14 @@ Hotspot Analysis
117117
``perf record`` and ``perf report`` can be used together to identify the
118118
functions in our code that consume the most CPU time:
119119

120-
.. code-block:: bash
120+
.. code-block:: console
121121
122122
$ sudo perf record -g -p <pid_of_server> -o perf.data
123123
124124
After running our server under load (For example, using ApacheBench tool),
125125
we can stop the recording and analyze the data using:
126126

127-
.. code-block:: bash
127+
.. code-block:: console
128128
129129
$ sudo perf report -i perf.data
130130
@@ -136,13 +136,13 @@ spending the most time.
136136
To do this, we need to convert the ``perf.data`` to a format that ``FlameGraph``
137137
can understand:
138138

139-
.. code-block:: bash
139+
.. code-block:: console
140140
141141
$ sudo perf script | ~/FlameGraph/stackcollapse-perf.pl > out.perf-folded
142142
143143
And, then, generate the ``FlameGraph``:
144144

145-
.. code-block:: bash
145+
.. code-block:: console
146146
147147
$ ~/FlameGraph/flamegraph.pl out.perf-folded > flamegraph.svg
148148

0 commit comments

Comments
 (0)