The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Translation

English type: Title =
OProfile
8/100 · 8

This translation is currently locked.

English Portuguese (Brazil) Actions
OProfile
OProfile
indexterm:[system analysis,OProfile,OProfile]indexterm:[OProfile] OProfile is a low overhead, system-wide performance monitoring tool. It uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system, such as when memory is referenced, the number of L2 cache requests, and the number of hardware interrupts received. On a {MAJOROS} system, the `oprofile` package must be installed to use this tool.
indexterm:[análise de sistema, OProfile, OProfile]indexterm:[OProfile] O OProfile é uma ferramenta de monitoramento de desempenho de sistema de baixa sobrecarga. Ele utiliza o hardware de monitoramento de desempenho no processador para obter informações sobre o kernel e executáveis no sistema, como referências de memória, número de solicitações de cache L2 e número de interrupções de hardware recebidas. Em um sistema {MAJOROS}, o pacote `oprofile` deve ser instalado para usar essa ferramenta.
Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more _counters_ that are incremented each time an event takes place. When the counter value increments, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
Muitos processadores incluem hardware dedicado de monitoramento de desempenho. Esse hardware permite detectar quando certos eventos ocorrem (como os dados solicitados não estarem na memória cache). O hardware geralmente se apresenta na forma de um ou mais _contadores_ que são incrementados cada vez que um evento ocorre. Quando o valor do contador incrementa, um interrupt é gerado, possibilitando controlar o nível de detalhe (e, portanto, o overhead) produzido pelo monitoramento de desempenho.
OProfile uses this hardware (or a timer-based substitute in cases where performance monitoring hardware is not present) to collect _samples_ of performance-related data each time a counter generates an interrupt. These samples are periodically written out to disk; later, the data contained in these samples can then be used to generate reports on system-level and application-level performance.
Muitos processadores incluem hardware dedicado de monitoramento de desempenho. Esse hardware torna possível detectar quando certos eventos ocorrem (como os dados solicitados não estarem na memória cache). O hardware geralmente se apresenta na forma de um ou mais _contadores_ que são incrementados cada vez que um evento ocorre. Quando o valor do contador incrementa, um interrupt é gerado, possibilitando controlar o nível de detalhe (e, portanto, o overhead) produzido pelo monitoramento de desempenho.
Be aware of the following limitations when using OProfile:
 
*Use of shared libraries* — Samples for code in shared libraries are not attributed to the particular application unless the [option]`--separate=library` option is used.
 
*Performance monitoring samples are inexact* — When a performance monitoring register triggers a sample, the interrupt handling is not precise like a divide by zero exception. Due to the out-of-order execution of instructions by the processor, the sample may be recorded on a nearby instruction.
 
*pass:attributes[{blank}][command]#opreport# does not associate samples for inline functions properly* — [command]#opreport# uses a simple address range mechanism to determine which function an address is in. Inline function samples are not attributed to the inline function but rather to the function the inline function was inserted into.
 
*OProfile accumulates data from multiple runs* — OProfile is a system-wide profiler and expects processes to start up and shut down multiple times. Thus, samples from multiple runs accumulate. Use the command [command]#opcontrol --reset# to clear out the samples from previous runs.
 
*Hardware performance counters do not work on guest virtual machines* — Because the hardware performance counters are not available on virtual systems, you need to use the `timer` mode. Enter the command [command]#opcontrol --deinit#, and then execute [command]#modprobe oprofile timer=1# to enable the `timer` mode.
 
*Non-CPU-limited performance problems* — OProfile is oriented to finding problems with CPU-limited processes. OProfile does not identify processes that are asleep because they are waiting on locks or for some other event to occur (for example an I/O device to finish an operation).
 
Overview of Tools
 
indexterm:[OProfile,overview of tools] xref:OProfile.adoc#tb-oprofile-tools[OProfile Commands] provides a brief overview of the most commonly used tools provided with the `oprofile` package.
 
OProfile Commands
 
|Command|Description
|[command]#ophelp#|Displays available events for the system's processor along with a brief description of each.
|[command]#opimport#|Converts sample database files from a foreign binary format to the native format for the system. Only use this option when analyzing a sample database from a different architecture.
|[command]#opannotate#|Creates annotated source for an executable if the application was compiled with debugging symbols. See xref:OProfile.adoc#s2-oprofile-reading-opannotate[Using [command]#opannotate#] for details.
|[command]#opcontrol#|Configures what data is collected. See xref:OProfile.adoc#s1-oprofile-configuring[Configuring OProfile Using Legacy Mode] for details.
|[command]#operf#|Recommended tool to be used in place of [command]#opcontrol# for profiling. See xref:OProfile.adoc#s1-using-operf[Using operf] for details.
For differences between [command]#operf# and [command]#opcontrol# see xref:OProfile.adoc#s2-operf_vs_opcontrol[operf vs. opcontrol].
|[command]#opreport#|Retrieves profile data. See xref:OProfile.adoc#s2-oprofile-reading-opreport[Using [command]#opreport#] for details.
|[command]#oprofiled#|Runs as a daemon to periodically write sample data to disk.
 
operf vs. opcontrol
 

Loading…

User avatar farribeiro

Translation added
OProfile
OProfile
11 months ago
User avatar farribeiro

Contributor joined
Contributor joined 11 months ago
User avatar None

String updated in the repository
OProfile
 
11 months ago
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

String information

Source string description
type: Title =
Flags
no-wrap
Source string location
./pages/monitoring-and-automation/OProfile.adoc:6
String age
11 months ago
Last updated
11 months ago
Source string age
2 years ago
Translation file
po/pt_BR/f36/pages/monitoring-and-automation/OProfile.po, string 1