sysprof sysprof-45 - en to eu translation catalogue (38 entries)

note: (itstool) path: section/title (itstool) path: page/title
en: Profiling
eu: Profilatzea

note: (itstool) path: section/title
en: Frequently Asked Questions
eu: Ohiko galderak

note: (itstool) path: info/desc
en: Welcome to <app>Sysprof</app>!
eu: Ongi etorri <app>Sysprof</app> aplikaziora!

note: (itstool) path: page/title
en: Introduction
eu: Sarrera

note: (itstool) path: page/p
en: <app>Sysprof</app> is a system profiler for Linux that targets the GNOME desktop.
eu: <app>Sysprof</app> Linuxeko GNOME mahaiganerako sistema-profilatzaile bat da.

note: (itstool) path: info/desc
en: Differences between tracing and sampling
eu: Aztarnak jarraitzearen eta laginak hartzearen arteko desberdintasunak

note: (itstool) path: section/title
en: What is a Profiler?
eu: Zer da profilatzaile bat?

note: (itstool) path: section/p
en: A profiler is an application that records information about an application or system while it runs. That information can be explored to gain insight into how the application could be changed to perform better.
eu: Profilatzaileak aplikazio bati edo sistema bati buruzko informazioa, haiek exekutatzen ari diren bitartean, erregistratzen duten aplikazioak dira.

note: (itstool) path: section/p
en: Two common categories of software profilers exist, commonly referred to as either tracing or sampling profilers. What is meant by tracing profiler is that every function call executed by the program is known to the profiler. A sampling profiler works by inspecting the state of the program on a regular frequency and therefore does not see every function call executed by the program.
eu: Profilatzaileen bi kategoria daude: aztarnak jarraitzen dutenak eta laginak hartzen dituztenak. Aztarnen jarraitzaileetan, profilatzaileak programak exekutatutako funtzio-dei bakoitzaren jarraipena egiten du. Laginen profilatzaileetan, programaren egoera ikuskatzen da aldian behin eta, beraz, ez ditu ikusten programak exekutatu dituen funtzio-dei guztiak.

note: (itstool) path: section/p
en: Both tracing and sampling profilers have their advantages. A notable advantage of a sampling profiler is that the overhead is much less than that of a tracing profiler, making it easier to use for software that requires interactivity.
eu: Mota bakoitzak bere abantailak ditu. Laginen bidezko profilatzaileen abantaila nabarmenetako bat da zeharkako lan gutxiago egin behar dela eta, beraz, elkarreraginkortasuna behar duten softwarearekin errazago erabiltzen direla.

note: (itstool) path: section/p
en: <app>Sysprof</app> is a sampling profiler.
eu: <app>Sysprof</app> laginen profilatzailea da.

note: (itstool) path: section/title
en: How to profile your system
eu: Nola profilatu zure sistema

note: (itstool) path: section/p
en: To profile your entire system, ensure the target button is set to <em>All Processes</em> and click <em>Record</em>.
eu: Sistema osoa profilatzeko, ziurtatu helburuko botoian <em>Prozesu guztiak</em> ezarrita dagoela eta egin klik <em>Grabatu</em> aukeran.

note: (itstool) path: section/p
en: At this point, you may be asked to <em>authorize</em> access to profile the system. This is required as the Linux kernel's perf implementation requires root to perform whole-system profiling.
eu: Une horretan, sistema profilatzeko <em>baimena</em> eskatuko dizu aplikazioak. Hori derrigorrezkoa da, Linuxen kernelaren perf inplementazioak erro izatera derrigortzen baitu sistema osoa profilatzeko.

note: (itstool) path: section/p
en: During the profiling session, you will see the number of seconds the profile has been active. Clicking the <em>Record</em> button again will stop the profiling session. Afterwhich, the callgraph will be displayed.
eu: Profilatze-saioan zehar, profila aktibo egon den segundo kopurua ikusiko duzu. <em>Grabatu</em> botoian berriro sakatuta, profilatze-saioa amaitu egingo da. Ondoren, dei-grafoa bistaratuko da.

note: (itstool) path: note/p
en: If you find that the <app>sysprof</app> application is showing up in your profiling callgraph, you might consider recording the profiling session with <cmd>sysprof-cli</cmd>. This is a command line program that will capture your profiling session to disk to be viewed at a later time.
eu: s

note: (itstool) path: section/p
en: See <link href="profiling#interpreting-results">interpreting results</link> for more guidance.
eu: Begiratu <link href="profiling#interpreting-results">emaitzak interpretatzea</link> informazio gehiagorako.

note: (itstool) path: section/title
en: Profile a new process
eu: Profilatu prozesu berri bat

note: (itstool) path: section/p
en: Often times, you may need to spawn a new process to profile. First, select the <em>Application</em> button next at the top of the recording window. Fill in your command and working directory, and optionally specify any environment variables you need. Your process will be started when recording begins.
eu: Zenbaitetan, prozesu berri bat abiarazi behar da hura profilatzeko. Lehenengo, hautatu grabazio-leihoaren goiko aldean dagoen <em>Aplikazioa</em> botoia, eta, aukeran, zehaztu beharko dituzun ingurune-aldagaiak. Zure prozesua grabazioa hastean abiaraziko da.

note: (itstool) path: note/p
en: If you are spawning a process that requires access to your current display, such as a GTK+ application, you will want to make sure <em>Inherit current environment</em> is set.
eu: Zure uneko pantaila atzitzea behar duen prozesu bat, adibidez GTK+ aplikazio bat, abiarazi baduzu, ziurtatu <em>Heredatu uneko ingurunea</em> ezarrita dagoela.

note: (itstool) path: section/title
en: Profiling with the sysprof-cli command line tool
eu: sysprof-cli komando-lerroko tresnarekin profilatzea

note: (itstool) path: section/p
en: For minimal overhead, you might consider using the <cmd>sysprof-cli</cmd> command line tool. When run without any arguments, it will record your entire system and save the output to <file>capture.syscap</file>. This file can be opened with the <app>Sysprof</app> application to view the callgraph.
eu: Zeharkako lan gutxien egin nahi baduzu, komando-lerroko <cmd>sysprof-cli</cmd> tresna erabili dezakezu. Argumenturik gabe exekutatzen bada, sistema osoa grabatuko du eta irteera <file>capture.syscap</file> fitxategian gordeko du. Fitxategia <app>Sysprof</app> aplikazioarekin ireki daiteke dei-grafoa ikusteko.

note: (itstool) path: section/p
en: If you would like to spawn a new process, use <cmd>sysprof-cli -- 'command'</cmd> to specify a command to be launched. The command will inherit the current environment.
eu: Prozesu berri abiarazi nahi baduzu, erabili <cmd>sysprof-cli -- 'komandoa'</cmd> komando bat zehazteko.Komandoak uneko ingurunea heredatuko du

note: (itstool) path: section/title
en: Interpreting results
eu: Emaitzak interpretatzea

note: (itstool) path: section/p
en: The profiling results in <app>Sysprof</app> are split into three sections. On the top left is a list of all the functions profiled. They are sorted by how often they were called during the recording.
eu: <app>Sysprof</app> aplikazioaren profilatze-emaitzak hiru ataletan daude banatuta. Goian ezkerrean, profilatutako funtzio guztien zerrenda bat agertzen da. Grabazioan zehar zenbat aldiz deituak izan diren, horren arabera egongo dira ordenatuta.

note: (itstool) path: note/p
en: It is important to note that the amount of time spent in each function is not captured. That would require a tracing profiler to accurately record. The percentage is calculated by determining how often that function showed up in the current stacktrace when a sample was recorded.
eu: Kontuan izan ez dela kapturatzen funtzio bakoitza zenbat denbora egon den abian. Horrek aztarnen profilatzea beharko luke, grabazioa zehatza izan zedin. Ehunekoa kalkulatzeko, lagin bat grabatzen ari zenean funtzioa uneko pila-aztarnan zenba aldiz agertu den erabiltzen da.

note: (itstool) path: section/p
en: After selecting a function from the functions list, all of the recorded callers of that function will be displayed on the bottom left. They are also sorted by the percentage of samples that included that function in the stacktrace.
eu: Funtzioen zerrendan funtzio bat hautatu ondoren, funtzio horretarako grabatutako deitzaile guztiak behean ezkerrean bistaratuko dira. Funtzioa pila-aztarnan duten laginen ehunekoaren arabera ordenatzen dira horiek ere.

note: (itstool) path: section/p
en: On the right, are all of the decendants of a selected function. You can select a function either from the functions list, or the callers list.
eu: Eskuinean, hautatutako funtzioaren ondorengo guztiak ageriko dira. Funtzio bat hautatu nahi izanez gero, funtzioen zerrendan edo deitzaileen zerrendan hautatu daiteke.

note: (itstool) path: page/title
en: What does heap mean?
eu: Zer esan nahi "pila" hitzak?

note: (itstool) path: section/title
en: What does "In file [heap]" mean?
eu: Zer esan nahi du "Fitxategian [pila]" aukerak?

note: (itstool) path: section/title
en: JIT (Just in Time) compilers
eu: JIT (Just in Time) konpilatzaileak

note: (itstool) path: section/p
en: Languages like Java can generate executable code while a program is running and store it in the heap. Sysprof is accurately reporting the situation in this case.
eu: Java eta antzeko lengoaiek kode exekutagarria sortu dezakete programa exekutatzen ari den bitartean, eta pilan gorde dezakete. Kasu horretan, Sysprof aplikazioak zehaztasunez emango du egoeraren berri.

note: (itstool) path: section/title
en: Optimizing compilers
eu: Konpilatzaileak optimizatzea

note: (itstool) path: section/p
en: C and C++ compilers can optimize away information needed to determine a function's caller, so it is mistaken for [heap]. You can still tell how often each function is called by the program, but not always from where.
eu: C eta C++ konpilatzaileek funtzio baten deitzailea zehazteko behar den informazioa kendu dezakete eta [pila]rekin nahastu daiteke. Hortaz, programak funtzio bakoitza zenbat aldiz deitzen duen jakin daiteke, baina ez nondik deitu duen.

note: (itstool) path: note/p
en: For gcc, the flag <code>-fno-omit-frame-pointer</code> will prevent this optimization. The flag is not always needed, for example on x86_64 machines it is only needed with -O3 optimization.
eu: gcc-ren kasuan, <code>-fno-omit-frame-pointer</code> banderak optimizazio hori eragotziko du. Bandera ez da beti beharrezkoa, adibidez x86_64 makinetan -O3 optimizazioarekin soilik da beharrezkoa.

note: (itstool) path: note/p
en: To get the most detailed and accurate call tree from un-optimized code, use these flags: <code>-ggdb -fno-omit-frame-pointer -O0</code>
eu: Optimizatu gabeko kode baten dei-zuhaitz zehatza eta xehea eskuratzeko, erabili honako banderak: <code>-ggdb -fno-omit-frame-pointer -O0</code>

note: (itstool) path: license/p
en: This work is licensed under a <_:link-1/> license.
eu: Lan honen lizentzia <_:link-1/> da.

note: (itstool) path: license/p
en: As a special exception, the copyright holders give you permission to copy, modify, and distribute the example code contained in this documentation under the terms of your choosing, without restriction.
eu: Salbuespen berezi gisa, copyright jabeek baimena ematen dizute dokumentazio honetan dagoen kodea kopiatu, aldatu eta banatzeko zuk aukeratzen duzun lizentziaren arabera, inolako mugarik gabe.
