@@ -511,6 +511,9 @@ msgid ""
511
511
"but you can change the size by passing it after a comma like ``--call-graph "
512
512
"dwarf,16384``."
513
513
msgstr ""
514
+ "当使用 ``--call-graph dwarf`` 时,``perf`` 工具将对被分析进程的栈打快照并将信息保存在 ``perf.data`` "
515
+ "文件中。 在默认情况下,栈转储的大小为 8192 字节,但你可以通过额外传入一个逗号加数值如 ``--call-graph dwarf,16384`` "
516
+ "来改变这个大小。"
514
517
515
518
#: ../../howto/perf_profiling.rst:263
516
519
msgid ""
@@ -520,6 +523,8 @@ msgid ""
520
523
"be able to sample the process as frequently as it would like as the overhead"
521
524
" will be higher."
522
525
msgstr ""
526
+ "栈转储的大小很重要因为如果这个值太小 ``perf`` 将无法展开栈信息而输出将不完整。 另一方面,如果这个值太大,那么 ``perf`` "
527
+ "将无法按需以足够的频率对进程执行采样因为那样资源开销会过高。"
523
528
524
529
#: ../../howto/perf_profiling.rst:269
525
530
msgid ""
@@ -529,16 +534,20 @@ msgid ""
529
534
" Python functions in your profiling output, try increasing the stack dump "
530
535
"size to 65528 bytes (the maximum)::"
531
536
msgstr ""
537
+ "栈大小在对使用较低优化级别 (如 ``-O0``) 编译的 Python 代码进行性能分析时更为重要,因为这类构建版往往有更大的栈帧。 如果你是使用 "
538
+ "``-O0`` 来编译 Python 并且没有在你的性能分析输出中看到 Python 函数,请尝试将栈转储大小增加到 65528 字节 (最大值)::"
532
539
533
540
#: ../../howto/perf_profiling.rst:275
534
541
msgid ""
535
542
"$ perf record -F 9999 -g -k 1 --call-graph dwarf,65528 -o perf.data python "
536
543
"-Xperf_jit my_script.py"
537
544
msgstr ""
545
+ "$ perf record -F 9999 -g -k 1 --call-graph dwarf,65528 -o perf.data python "
546
+ "-Xperf_jit my_script.py"
538
547
539
548
#: ../../howto/perf_profiling.rst:277
540
549
msgid "Different compilation flags can significantly impact stack sizes:"
541
- msgstr ""
550
+ msgstr "不同的编译旗标可能显著地影响栈大小: "
542
551
543
552
#: ../../howto/perf_profiling.rst:279
544
553
msgid ""
0 commit comments