1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
---
title: Performance
slug: Mozilla/Performance
tags:
- NeedsTranslation
- Performance
- TopicStub
translation_of: Mozilla/Performance
---
<p>Os links dos artigos aqui o ajudarão a melhorar a performance, se você estiver desenvolvendo um código de núcleo da Mozilla ou uma extensão.</p>
<table class="topicpage-table">
<tbody>
<tr>
<td>
<h3 id="Documentação">Documentação</h3>
<dl>
<dt><a href="/en/Performance/Reporting_a_Performance_Problem" title="en/Performance/Reporting_a_Performance_Problem">Reportiando um problema de performance</a></dt>
<dd>Um amigável guia do usuário para reportar um problema de performance. Um ambiente de desenvolvimento não é necessário.</dd>
<dt><a href="/en/Extensions/Performance_best_practices_in_extensions" title="en/Extensions/Performance best practices in extensions">Melhores práticas de performance em extensões</a> </dt>
<dd>Um guia de "melhores práticas" para desenvolvedores de extensões.</dd>
<dt><a href="/en/Performance/Measuring_add-on_startup_performance" title="en/Measuring Add-on Startup Performance">Medição da performance de inicialização da extensão</a></dt>
<dd>Um guia para desenvolvedores de extensões de como configurar um ambiente de teste de performance.</dd>
<dt><a href="/en/XUL_School/Appendix_A:_Add-on_Performance" title="en/XUL School/Appendix A: Add-on Performance">Escola XUL: Performance em Extensões</a></dt>
<dd>Dicas para desenvolvedores de extensões para ajudá-los a evitar prejudicar a performance do aplicativo.</dd>
<dt><a href="/en/Performance/GPU_performance" title="en/GPU performance">Performance do GPU</a></dt>
<dd>Dicas de criação de perfil e melhorias de performance com o uso de uma GPU.</dd>
</dl>
<p><span class="alllinks"><a class="internal" href="/Special:Tags?tag=Performance" title="Special:Tags?tag=Performance">Veja todas as páginas com a marca "Performance"...</a></span></p>
<h3 id="Ferramentas_de_criação_de_perfil_e_detecção_de_perdas_de_memória">Ferramentas de criação de perfil e detecção de perdas de memória</h3>
<dl>
<dt><a href="/en-US/docs/Mozilla/Performance/about:memory">about:memory</a></dt>
<dd>about:memory é a ferramenta mais fácil para medir o uso em código Mozilla, e o melhor lugar para começar. Também deixa você fazer outras operações relacionadas à memória como chamar GC e CC, esvaziar os logs de GC e CC, e esvaziar os relatórios de DMD. about:memory é feito no topo da infraestrutura de relatório de memória do Firefox.</dd>
<dt><a href="/en-US/docs/Mozilla/Performance/DMD">DMD</a></dt>
<dd>DMD é uma ferramenta que identifica deficiências nas medidas do about:memory, e também pode fazer múltiplos tipos de criação de perfis de pilha.</dd>
<dt><a href="https://areweslimyet.com/">areweslimyet.com</a></dt>
<dd>areweslimyet.com (a.k.a. AWSY) is a memory usage and regression tracker.</dd>
<dt><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance/BloatView">BloatView</a></dt>
<dd>BloatView prints per-class statistics on allocations and refcounts, and provides gross numbers on the amount of memory being leaked broken down by class. It is used as part of Mozilla's continuous integration testing.</dd>
<dt><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Refcount_tracing_and_balancing">Refcount tracing and balancing</a></dt>
<dd>Refcount tracing and balancing are ways to track down leaks caused by incorrect uses of reference counting. They are slow and not particular easy to use, and thus most suitable for use by expert developers.</dd>
<dt><a href="/en-US/docs/Mozilla/Performance/GC_and_CC_logs">GC and CC logs</a></dt>
<dd>GC and CC logs can be generated and analyzed to in various ways. In particular, they can help you understand why a particular object is being kept alive.</dd>
<dt><a href="/en-US/docs/Mozilla/Testing/Valgrind">Valgrind</a></dt>
<dd><a class="external text" href="http://valgrind.org/" rel="nofollow">Valgrind</a> is a tool that detects various memory-related problems at runtime, including leaks. Valgrind is used as <a class="external text" href="/en-US/docs/Valgrind_test_job" rel="nofollow">part</a> of Mozilla's continuous integration testing, though the coverage is limited because Valgrind is slow.</dd>
<dt><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Firefox_and_Address_Sanitizer#LeakSanitizer">LeakSanitizer</a></dt>
<dd><span class="external text">LeakSanitizer</span> (a.k.a. LSAN) is similar to Valgrind, but it runs faster because it uses static source code instrumentation. LSAN is part of Mozilla's continuous integration testing, with most tests running through it as part of the AddressSanitizer (a.k.a. ASAN) test jobs.</dd>
<dt><a href="http://developer.apple.com/documentation/Performance/Conceptual/ManagingMemory/Articles/FindingLeaks.html">Apple tools</a></dt>
<dd>Apple provides <span class="external text">some tools</span> for Mac OS X that report similar problems to those reported by LSAN and Valgrind. The "leaks" tool is not recommended for use with SpiderMonkey or Firefox, because it gets confused by tagged pointers and thinks objects have leaked when they have not (see <a class="external text" href="https://bugzilla.mozilla.org/show_bug.cgi?id=390944" rel="nofollow">bug 390944</a>).</dd>
<dt><a href="/en-US/docs/Mozilla/Performance/Leak_Gauge">Leak Gauge</a></dt>
<dd>Leak Gauge is a tool that can be used to detect certain kinds of leaks in Gecko, including those involving documents, window objects, and docshells.</dd>
<dt><a href="http://dxr.mozilla.org/mozilla-central/source/memory/replace/logalloc/README">LogAlloc</a></dt>
<dd>LogAlloc is a tool that dumps a log of memory allocations in Gecko. That log can then be replayed against Firefox's default memory allocator independently or through another replace-malloc library, allowing the testing of other allocators under the exact same workload.</dd>
</dl>
<p>See also the documentation on <a href="/en-US/docs/Mozilla/Performance/Leak-hunting_strategies_and_tips">Leak-hunting strategies and tips.</a></p>
</td>
<td>
<h3 id="Profiling_and_performance_tools">Profiling and performance tools</h3>
<dl>
<dt><a href="/en/Performance/Profiling_with_the_Built-in_Profiler" title="en/Performance/Profiling with the Built-in Profiler">Profiling with the Built-in Profiler</a> {{ gecko_minversion_inline("16.0") }}</dt>
<dd>The built-in profiler is a good tool to start with.</dd>
<dt><a href="/en/Performance/Profiling_with_Instruments" title="en/Performance/Profiling with Instruments">Profiling with Instruments</a></dt>
<dd>How to use Apple's Instruments tool to profile Mozilla code.</dd>
<dt><a href="/en/Performance/Profiling_with_Xperf" title="en/Performance/Profiling with Xperf">Profiling with Xperf</a></dt>
<dd>How to use Microsoft's Xperf tool to profile Mozilla code.</dd>
<dt><a href="/en/Performance/Profiling_with_Zoom" title="en/Performance/Profiling with Zoom">Profiling with Zoom</a></dt>
<dd>Zoom is a profiler for Linux done by the people who made Shark</dd>
<dt><a href="/en/Performance/Measuring_performance_using_the_PerfMeasurement.jsm_code_module" title="en/Performance/Measuring performance using the PerfMeasurement.jsm code module">Measuring performance using the PerfMeasurement.jsm code module</a> {{ gecko_minversion_inline("2.0") }}</dt>
<dd>Using <a href="/en/JavaScript_code_modules/PerfMeasurement.jsm" title="en/JavaScript code modules/PerfMeasurement.jsm"><code>PerfMeasurement.jsm</code></a> to measure performance data in your JavaScript code.</dd>
<dt><a href="/en-US/docs/Performance/Adding_a_new_Telemetry_probe" title="https://developer.mozilla.org/en-US/docs/Performance/Adding_a_new_Telemetry_probe">Adding a new Telemetry probe</a></dt>
<dd>Information on how to add a new measurement to the Telemetry performance-reporting system</dd>
<dt><a href="/en/Performance/Profiling_JavaScript_with_Shark" title="en/Performance/Profiling JavaScript with Shark">Profiling JavaScript with Shark</a> {{ gecko_minversion_inline("1.9") }}</dt>
<dd>How to use the Mac OS X Shark profiler to profile JavaScript code in Firefox 3.5 or later.</dd>
<dt><a href="/en/Performance/Profiling_with_Shark" title="en/Performance/Profiling with Shark">Profiling with Shark</a></dt>
<dd>How to use Apple's Shark tool to profile Mozilla code.</dd>
<dt><a href="/en-US/docs/Mozilla/Performance/Investigating_CSS_Performance">Investigating CSS Performance</a></dt>
<dd>How to figure out why restyle is taking so long</dd>
</dl>
<h3 id="Related_Topics">Related Topics</h3>
<dl>
<dd><a href="/en/JavaScript" title="en/JavaScript">JavaScript</a>, <a href="/en/XPCOM" title="en/XPCOM">XPCOM</a>, <a href="/En/Developer_Guide" title="en/Developing_Mozilla">Developing Mozilla</a>, <a href="/en/Extensions" title="en/Extensions">Extensions</a>, <a href="/en/Addons" title="en/Addons">Addons</a></dd>
</dl>
</td>
</tr>
</tbody>
</table>
<p> </p>
|
