@@ -12,7 +12,7 @@ msgid ""
12
12
msgstr ""
13
13
"Project-Id-Version : Python 3.13\n "
14
14
"Report-Msgid-Bugs-To : \n "
15
- "POT-Creation-Date : 2025-03-28 14:18+0000\n "
15
+ "POT-Creation-Date : 2025-04-18 14:18+0000\n "
16
16
"PO-Revision-Date : 2023-05-24 13:07+0000\n "
17
17
"Last-Translator : Stan Ulbrych, 2025\n "
18
18
"Language-Team : Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -364,13 +364,47 @@ msgid ""
364
364
msgstr ""
365
365
366
366
msgid ""
367
- "Notice that when using ``--call-graph dwarf`` the ``perf`` tool will take "
368
- "snapshots of the stack of the process being profiled and save the "
369
- "information in the ``perf.data`` file. By default the size of the stack dump "
370
- "is 8192 bytes but the user can change the size by passing the size after "
371
- "comma like ``--call-graph dwarf,4096``. The size of the stack dump is "
372
- "important because if the size is too small ``perf`` will not be able to "
373
- "unwind the stack and the output will be incomplete. On the other hand, if "
374
- "the size is too big, then ``perf`` won't be able to sample the process as "
375
- "frequently as it would like as the overhead will be higher."
367
+ "When using ``--call-graph dwarf``, the ``perf`` tool will take snapshots of "
368
+ "the stack of the process being profiled and save the information in the "
369
+ "``perf.data`` file. By default, the size of the stack dump is 8192 bytes, "
370
+ "but you can change the size by passing it after a comma like ``--call-graph "
371
+ "dwarf,16384``."
372
+ msgstr ""
373
+
374
+ msgid ""
375
+ "The size of the stack dump is important because if the size is too small "
376
+ "``perf`` will not be able to unwind the stack and the output will be "
377
+ "incomplete. On the other hand, if the size is too big, then ``perf`` won't "
378
+ "be able to sample the process as frequently as it would like as the overhead "
379
+ "will be higher."
380
+ msgstr ""
381
+
382
+ msgid ""
383
+ "The stack size is particularly important when profiling Python code compiled "
384
+ "with low optimization levels (like ``-O0``), as these builds tend to have "
385
+ "larger stack frames. If you are compiling Python with ``-O0`` and not seeing "
386
+ "Python functions in your profiling output, try increasing the stack dump "
387
+ "size to 65528 bytes (the maximum)::"
388
+ msgstr ""
389
+
390
+ msgid ""
391
+ "$ perf record -F 9999 -g -k 1 --call-graph dwarf,65528 -o perf.data python -"
392
+ "Xperf_jit my_script.py"
393
+ msgstr ""
394
+
395
+ msgid "Different compilation flags can significantly impact stack sizes:"
396
+ msgstr ""
397
+
398
+ msgid ""
399
+ "Builds with ``-O0`` typically have much larger stack frames than those with "
400
+ "``-O1`` or higher"
401
+ msgstr ""
402
+
403
+ msgid ""
404
+ "Adding optimizations (``-O1``, ``-O2``, etc.) typically reduces stack size"
405
+ msgstr ""
406
+
407
+ msgid ""
408
+ "Frame pointers (``-fno-omit-frame-pointer``) generally provide more reliable "
409
+ "stack unwinding"
376
410
msgstr ""
0 commit comments