-
-
Notifications
You must be signed in to change notification settings - Fork 13
Expand file tree
/
Copy pathperf_profiling.po
More file actions
409 lines (359 loc) · 14.8 KB
/
perf_profiling.po
File metadata and controls
409 lines (359 loc) · 14.8 KB
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
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2026, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# python-doc bot, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.13\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-04-03 15:26+0000\n"
"PO-Revision-Date: 2025-09-15 01:03+0000\n"
"Last-Translator: python-doc bot, 2025\n"
"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid "Python support for the Linux ``perf`` profiler"
msgstr ""
msgid "author"
msgstr "autor"
msgid "Pablo Galindo"
msgstr ""
msgid ""
"`The Linux perf profiler <https://perf.wiki.kernel.org>`_ is a very powerful "
"tool that allows you to profile and obtain information about the performance "
"of your application. ``perf`` also has a very vibrant ecosystem of tools "
"that aid with the analysis of the data that it produces."
msgstr ""
msgid ""
"The main problem with using the ``perf`` profiler with Python applications "
"is that ``perf`` only gets information about native symbols, that is, the "
"names of functions and procedures written in C. This means that the names "
"and file names of Python functions in your code will not appear in the "
"output of ``perf``."
msgstr ""
msgid ""
"Since Python 3.12, the interpreter can run in a special mode that allows "
"Python functions to appear in the output of the ``perf`` profiler. When this "
"mode is enabled, the interpreter will interpose a small piece of code "
"compiled on the fly before the execution of every Python function and it "
"will teach ``perf`` the relationship between this piece of code and the "
"associated Python function using :doc:`perf map files <../c-api/perfmaps>`."
msgstr ""
msgid ""
"Support for the ``perf`` profiler is currently only available for Linux on "
"select architectures. Check the output of the ``configure`` build step or "
"check the output of ``python -m sysconfig | grep HAVE_PERF_TRAMPOLINE`` to "
"see if your system is supported."
msgstr ""
msgid "For example, consider the following script:"
msgstr ""
msgid ""
"def foo(n):\n"
" result = 0\n"
" for _ in range(n):\n"
" result += 1\n"
" return result\n"
"\n"
"def bar(n):\n"
" foo(n)\n"
"\n"
"def baz(n):\n"
" bar(n)\n"
"\n"
"if __name__ == \"__main__\":\n"
" baz(1000000)"
msgstr ""
msgid "We can run ``perf`` to sample CPU stack traces at 9999 hertz::"
msgstr ""
msgid "$ perf record -F 9999 -g -o perf.data python my_script.py"
msgstr ""
msgid "Then we can use ``perf report`` to analyze the data:"
msgstr ""
msgid ""
"$ perf report --stdio -n -g\n"
"\n"
"# Children Self Samples Command Shared Object Symbol\n"
"# ........ ........ ............ .......... .................. ..........................................\n"
"#\n"
" 91.08% 0.00% 0 python.exe python.exe [.] "
"_start\n"
" |\n"
" ---_start\n"
" |\n"
" --90.71%--__libc_start_main\n"
" Py_BytesMain\n"
" |\n"
" |--56.88%--pymain_run_python.constprop.0\n"
" | |\n"
" | |--56.13%--_PyRun_AnyFileObject\n"
" | | _PyRun_SimpleFileObject\n"
" | | |\n"
" | | |--55.02%--run_mod\n"
" | | | |\n"
" | | | --54.65%--"
"PyEval_EvalCode\n"
" | | | "
"_PyEval_EvalFrameDefault\n"
" | | | "
"PyObject_Vectorcall\n"
" | | | "
"_PyEval_Vector\n"
" | | | "
"_PyEval_EvalFrameDefault\n"
" | | | "
"PyObject_Vectorcall\n"
" | | | "
"_PyEval_Vector\n"
" | | | "
"_PyEval_EvalFrameDefault\n"
" | | | "
"PyObject_Vectorcall\n"
" | | | "
"_PyEval_Vector\n"
" | | | |\n"
" | | | "
"|--51.67%--_PyEval_EvalFrameDefault\n"
" | | | "
"| |\n"
" | | | "
"| |--11.52%--_PyLong_Add\n"
" | | | "
"| | |\n"
" | | | "
"| | |--2.97%--_PyObject_Malloc\n"
"..."
msgstr ""
msgid ""
"As you can see, the Python functions are not shown in the output, only "
"``_PyEval_EvalFrameDefault`` (the function that evaluates the Python "
"bytecode) shows up. Unfortunately that's not very useful because all Python "
"functions use the same C function to evaluate bytecode so we cannot know "
"which Python function corresponds to which bytecode-evaluating function."
msgstr ""
msgid ""
"Instead, if we run the same experiment with ``perf`` support enabled we get:"
msgstr ""
msgid ""
"$ perf report --stdio -n -g\n"
"\n"
"# Children Self Samples Command Shared Object Symbol\n"
"# ........ ........ ............ .......... .................. .....................................................................\n"
"#\n"
" 90.58% 0.36% 1 python.exe python.exe [.] "
"_start\n"
" |\n"
" ---_start\n"
" |\n"
" --89.86%--__libc_start_main\n"
" Py_BytesMain\n"
" |\n"
" |--55.43%--pymain_run_python.constprop.0\n"
" | |\n"
" | |--54.71%--_PyRun_AnyFileObject\n"
" | | _PyRun_SimpleFileObject\n"
" | | |\n"
" | | |--53.62%--run_mod\n"
" | | | |\n"
" | | | --53.26%--"
"PyEval_EvalCode\n"
" | | | py::"
"<module>:/src/script.py\n"
" | | | "
"_PyEval_EvalFrameDefault\n"
" | | | "
"PyObject_Vectorcall\n"
" | | | "
"_PyEval_Vector\n"
" | | | py::baz:/"
"src/script.py\n"
" | | | "
"_PyEval_EvalFrameDefault\n"
" | | | "
"PyObject_Vectorcall\n"
" | | | "
"_PyEval_Vector\n"
" | | | py::bar:/"
"src/script.py\n"
" | | | "
"_PyEval_EvalFrameDefault\n"
" | | | "
"PyObject_Vectorcall\n"
" | | | "
"_PyEval_Vector\n"
" | | | py::foo:/"
"src/script.py\n"
" | | | |\n"
" | | | "
"|--51.81%--_PyEval_EvalFrameDefault\n"
" | | | "
"| |\n"
" | | | "
"| |--13.77%--_PyLong_Add\n"
" | | | "
"| | |\n"
" | | | "
"| | |--3.26%--_PyObject_Malloc"
msgstr ""
msgid "How to enable ``perf`` profiling support"
msgstr ""
msgid ""
"``perf`` profiling support can be enabled either from the start using the "
"environment variable :envvar:`PYTHONPERFSUPPORT` or the :option:`-X perf <-"
"X>` option, or dynamically using :func:`sys.activate_stack_trampoline` and :"
"func:`sys.deactivate_stack_trampoline`."
msgstr ""
msgid ""
"The :mod:`!sys` functions take precedence over the :option:`!-X` option, "
"the :option:`!-X` option takes precedence over the environment variable."
msgstr ""
msgid "Example, using the environment variable::"
msgstr ""
msgid ""
"$ PYTHONPERFSUPPORT=1 perf record -F 9999 -g -o perf.data python my_script."
"py\n"
"$ perf report -g -i perf.data"
msgstr ""
msgid "Example, using the :option:`!-X` option::"
msgstr ""
msgid ""
"$ perf record -F 9999 -g -o perf.data python -X perf my_script.py\n"
"$ perf report -g -i perf.data"
msgstr ""
msgid "Example, using the :mod:`sys` APIs in file :file:`example.py`:"
msgstr ""
msgid ""
"import sys\n"
"\n"
"sys.activate_stack_trampoline(\"perf\")\n"
"do_profiled_stuff()\n"
"sys.deactivate_stack_trampoline()\n"
"\n"
"non_profiled_stuff()"
msgstr ""
msgid "...then::"
msgstr ""
msgid ""
"$ perf record -F 9999 -g -o perf.data python ./example.py\n"
"$ perf report -g -i perf.data"
msgstr ""
msgid "How to obtain the best results"
msgstr ""
msgid ""
"For best results, Python should be compiled with ``CFLAGS=\"-fno-omit-frame-"
"pointer -mno-omit-leaf-frame-pointer\"`` as this allows profilers to unwind "
"using only the frame pointer and not on DWARF debug information. This is "
"because as the code that is interposed to allow ``perf`` support is "
"dynamically generated it doesn't have any DWARF debugging information "
"available."
msgstr ""
msgid ""
"You can check if your system has been compiled with this flag by running::"
msgstr ""
msgid "$ python -m sysconfig | grep 'no-omit-frame-pointer'"
msgstr "$ python -m sysconfig | grep 'no-omit-frame-pointer'"
msgid ""
"If you don't see any output it means that your interpreter has not been "
"compiled with frame pointers and therefore it may not be able to show Python "
"functions in the output of ``perf``."
msgstr ""
msgid "How to work without frame pointers"
msgstr ""
msgid ""
"If you are working with a Python interpreter that has been compiled without "
"frame pointers, you can still use the ``perf`` profiler, but the overhead "
"will be a bit higher because Python needs to generate unwinding information "
"for every Python function call on the fly. Additionally, ``perf`` will take "
"more time to process the data because it will need to use the DWARF "
"debugging information to unwind the stack and this is a slow process."
msgstr ""
msgid ""
"To enable this mode, you can use the environment variable :envvar:"
"`PYTHON_PERF_JIT_SUPPORT` or the :option:`-X perf_jit <-X>` option, which "
"will enable the JIT mode for the ``perf`` profiler."
msgstr ""
msgid ""
"Due to a bug in the ``perf`` tool, only ``perf`` versions higher than v6.8 "
"will work with the JIT mode. The fix was also backported to the v6.7.2 "
"version of the tool."
msgstr ""
msgid ""
"Note that when checking the version of the ``perf`` tool (which can be done "
"by running ``perf version``) you must take into account that some distros "
"add some custom version numbers including a ``-`` character. This means "
"that ``perf 6.7-3`` is not necessarily ``perf 6.7.3``."
msgstr ""
msgid ""
"When using the perf JIT mode, you need an extra step before you can run "
"``perf report``. You need to call the ``perf inject`` command to inject the "
"JIT information into the ``perf.data`` file.::"
msgstr ""
msgid ""
"$ perf record -F 9999 -g -k 1 --call-graph dwarf -o perf.data python -"
"Xperf_jit my_script.py\n"
"$ perf inject -i perf.data --jit --output perf.jit.data\n"
"$ perf report -g -i perf.jit.data"
msgstr ""
msgid "or using the environment variable::"
msgstr ""
msgid ""
"$ PYTHON_PERF_JIT_SUPPORT=1 perf record -F 9999 -g --call-graph dwarf -o "
"perf.data python my_script.py\n"
"$ perf inject -i perf.data --jit --output perf.jit.data\n"
"$ perf report -g -i perf.jit.data"
msgstr ""
msgid ""
"``perf inject --jit`` command will read ``perf.data``, automatically pick up "
"the perf dump file that Python creates (in ``/tmp/perf-$PID.dump``), and "
"then create ``perf.jit.data`` which merges all the JIT information together. "
"It should also create a lot of ``jitted-XXXX-N.so`` files in the current "
"directory which are ELF images for all the JIT trampolines that were created "
"by Python."
msgstr ""
msgid ""
"When using ``--call-graph dwarf``, the ``perf`` tool will take snapshots of "
"the stack of the process being profiled and save the information in the "
"``perf.data`` file. By default, the size of the stack dump is 8192 bytes, "
"but you can change the size by passing it after a comma like ``--call-graph "
"dwarf,16384``."
msgstr ""
msgid ""
"The size of the stack dump is important because if the size is too small "
"``perf`` will not be able to unwind the stack and the output will be "
"incomplete. On the other hand, if the size is too big, then ``perf`` won't "
"be able to sample the process as frequently as it would like as the overhead "
"will be higher."
msgstr ""
msgid ""
"The stack size is particularly important when profiling Python code compiled "
"with low optimization levels (like ``-O0``), as these builds tend to have "
"larger stack frames. If you are compiling Python with ``-O0`` and not seeing "
"Python functions in your profiling output, try increasing the stack dump "
"size to 65528 bytes (the maximum)::"
msgstr ""
msgid ""
"$ perf record -F 9999 -g -k 1 --call-graph dwarf,65528 -o perf.data python -"
"Xperf_jit my_script.py"
msgstr ""
msgid "Different compilation flags can significantly impact stack sizes:"
msgstr ""
msgid ""
"Builds with ``-O0`` typically have much larger stack frames than those with "
"``-O1`` or higher"
msgstr ""
msgid ""
"Adding optimizations (``-O1``, ``-O2``, etc.) typically reduces stack size"
msgstr ""
msgid ""
"Frame pointers (``-fno-omit-frame-pointer``) generally provide more reliable "
"stack unwinding"
msgstr ""