mirror of
https://github.com/godotengine/godot-docs-l10n.git
synced 2025-12-31 09:49:22 +03:00
227 lines
12 KiB
Plaintext
227 lines
12 KiB
Plaintext
# SOME DESCRIPTIVE TITLE.
|
|
# Copyright (C) 2014-present Juan Linietsky, Ariel Manzur and the Godot community (CC BY 3.0)
|
|
# This file is distributed under the same license as the Godot Engine package.
|
|
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
|
#
|
|
#, fuzzy
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: Godot Engine latest\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
"Language-Team: LANGUAGE <LL@li.org>\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:4
|
|
msgid "Tracing Profilers"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:6
|
|
msgid "Godot currently supports two tracing profilers: `Tracy <https://github.com/wolfpld/tracy>`__ and `Perfetto <https://perfetto.dev>`__."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:9
|
|
msgid "In order to use either of them, you'll need to build the engine from source. If you've never done this before, please read :ref:`these docs <doc_compiling_index>` for the platform you want to profile on. You'll need to perform the same steps here, but with some additional arguments for ``scons``."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:18
|
|
msgid "Tracy for Windows, Linux, and macOS"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:20
|
|
msgid "Tracy is an Open Source profiler that runs on a wide variety of platforms, including Windows, Linux, and macOS. While it is primarily a tracing profiler, it can also periodically sample data like a :ref:`sampling profiler <doc_sampling_profilers>`, giving some of the benefits of both approaches."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:27
|
|
msgid "Build Godot with Tracy support"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:29
|
|
msgid "First, clone the latest version of the Tracy source code (\"0.13.0\" at the time of writing) using Git:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:36
|
|
msgid "This will create a ``tracy`` directory - you can place this anywhere."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:38
|
|
msgid "Next, build the release templates for your platform using ``scons``, but adding the ``profiler=tracy profiler_path=path/to/tracy`` arguments with the real path to the ``tracy`` directory, as well as ``debug_symbols=yes`` to allow Tracy's sampling features to work."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:45
|
|
msgid "You don't have to build release templates, you could also build debug templates, or even the editor. However, it's generally recommended to profile release templates, because that is the version your players will use, and it will perform differently than other types of builds."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:50
|
|
msgid "For example, to build release templates for Windows:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:57
|
|
msgid "Get the Tracy \"server\""
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:59
|
|
msgid "In Tracy terminology, the application you are profiling is the \"client\", and the one receiving the data is the \"server\"."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:62
|
|
msgid "If you are on Windows, you can download a pre-built ``tracy-profiler.exe`` from the Tracy `releases page <https://github.com/wolfpld/tracy/releases>`_."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:65
|
|
msgid "However, if you're on Linux or macOS, you'll either need to find a pre-built binary from a package manager (like ``brew`` or ``nix``), or build it from source yourself."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:71
|
|
msgid "If you do use a pre-built binary, be sure to use the same version that you used when building Godot."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:75
|
|
msgid "Build the Tracy server from source"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:77
|
|
msgid "In order to build Tracy, you'll need to install ``cmake``, which can be downloaded from the `CMake website <https://cmake.org/download/>`_, or possibly installed via a package manager (like ``brew`` or ``nix``)."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:81
|
|
msgid "The full instructions for building Tracy from source can be found in the `Tracy manual <https://github.com/wolfpld/tracy/releases/latest/download/tracy.pdf>`_, but here is the TL;DR:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:91
|
|
msgid "This will place the binary at ``tracy/profiler/build/tracy-profiler`` or ``tracy/profiler/build/tracy-profiler.exe`` (on Windows)."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:95
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:198
|
|
msgid "Record a trace"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:97
|
|
msgid "Launch the Tracy server - you'll see something like this:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:101
|
|
msgid "Press \"connect\". This will ensure tracy makes a connection immediately when the game launches. If you forget to press \"connect\", Tracy will store system events in RAM, which can quickly blow up your memory usage (see the ``TRACY_ON_DEMAND`` documentation)."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:106
|
|
msgid "Now, export your game using the release templates you built above, and run it. As soon as both are running, and you have pressed the \"Connect\" button in Tracy, you'll see data coming in:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:112
|
|
msgid "When you think you've gathered enough data, press the \"Stop\" button. If you clicked somewhere and the box with the \"Stop\" button disappeared, you can click the top-left most icon to bring it back."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:117
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:216
|
|
msgid "Examining the trace"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:119
|
|
msgid "Here are some of the basic controls:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:121
|
|
msgid "Zoom in/out with the mouse wheel"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:122
|
|
msgid "Right click and drag to move forward/backward on the timeline"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:123
|
|
msgid "In the top bar, click the left and right arrow buttons by \"Frames\" to move a single frame on the timeline"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:125
|
|
msgid "To learn more, see the `Tracy manual <https://github.com/wolfpld/tracy/releases/latest/download/tracy.pdf>`_."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:129
|
|
msgid "Perfetto for Android"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:131
|
|
msgid "Perfetto is the default tracing system for Android. In fact, its system tracing service has been built into the platform since Android 9."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:135
|
|
msgid "Build Godot with Perfetto support"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:137
|
|
msgid "First, clone the latest version of the Perfetto source code (\"53.0\" at the time of writing) using Git:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:144
|
|
msgid "This will create a ``perfetto`` directory - you can place this anywhere."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:146
|
|
msgid "Next, build the Android debug or release templates for your architecture using ``scons`` (per :ref:`Compiling for Android <doc_compiling_for_android>`), but adding the ``profiler=perfetto profiler_path=path/to/perfetto`` arguments with the real path to the ``perfetto`` directory."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:153
|
|
msgid "It's generally recommended to profile release templates, because that is the version your players will use, and it will perform differently than other types of builds. However, in the case of Android, it can sometimes be useful to use debug templates, because Godot can only do remote debugging of games exported from debug templates."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:159
|
|
msgid "For example, to build the release templates for arm64:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:166
|
|
msgid "Configuration"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:168
|
|
msgid "Perfetto requires a configuration file to tell it which events to track."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:170
|
|
msgid "Create a file called ``godot.config`` inside of the ``perfetto`` directory with this content:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:200
|
|
msgid "Finally, launch your game on an Android device using the export templates you built earlier."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:203
|
|
msgid "When you're ready to record a trace (for example, when you've hit the part of your game that is exhibiting performance issues), you can use this script that comes with the Perfetto source code:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:212
|
|
msgid "This will record for 10 seconds (per the configuration), or until you press :kbd:`Ctrl + C`."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:218
|
|
msgid "As soon as that script exits, it will launch the Perfetto UI in a web browser."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:220
|
|
msgid "To see the Godot events, expand the row for your application by clicking on its Android \"Unique Name\" (Perfetto will also include some events from system services in the trace)."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:226
|
|
msgid "Then you can use the ``WASD`` keys to navigate the graph:"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:228
|
|
msgid "Press :kbd:`A` or :kbd:`D` to navigate forward or backward along the timeline"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:229
|
|
msgid "Press :kbd:`W` or :kbd:`S` to zoom in or out"
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:231
|
|
msgid "You'll probably need to zoom a bit before you're able to see the individual events from Godot."
|
|
msgstr ""
|
|
|
|
#: ../../docs/engine_details/development/debugging/profiling/tracing_profilers.rst:234
|
|
msgid "To learn more, see the `Perfetto UI documentation <https://perfetto.dev/docs/visualization/perfetto-ui>`_."
|
|
msgstr ""
|