# 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/using_cpp_profilers.rst:4
msgid "Using C++ profilers"
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:6
msgid "To optimize Godot's performance, you need to know what to optimize first. To this end, profilers are useful tools."
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:11
msgid "There is a :ref:`built-in GDScript profiler <doc_the_profiler>` in the editor, but using C++ profiler may be useful in cases where the GDScript profiler is not accurate enough or is missing information due to bugs in the profiler."
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:15
msgid "There are two main types of profilers: sampling profilers and tracing profilers."
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:17
msgid "Sampling profilers periodically interrupt the running program and take a \"sample\", which records which functions are running. Using this information, the profiler estimates which functions the program spent the most time in."
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:21
msgid "Tracing profilers work by recording application-specific events (such as the start and end of a single frame), producing a log called a \"trace\". The profiler can use the trace to produce a graph showing an accurate high-level timeline of what happened. However, any code that is not explicitly instrumented will not appear in a tracing profiler's timeline!"
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:27
msgid "Godot supports both sampling profilers and tracing profilers, and already includes the logging code for common Godot events for use with a tracing profiler!"
msgstr ""

#: ../../docs/engine_details/development/debugging/using_cpp_profilers.rst:30
msgid "Different problems may be easier to debug with one kind of profiler over the other, but it's difficult to provide a set of rules for which to use. Give both a try, and see what you can learn from them!"
msgstr ""