Bản dịch này đang trong quá trình.
The articles linked to from here will help you improve performance, whether you're developing core Mozilla code or an add-on.
- Reporting a Performance Problem
- A user friendly guide to reporting a performance problem. A development environment is not required.
- Performance best practices in extensions
- A performance "best practices" guide for extension developers.
- Measuring Add-on Startup Performance
- A guide for add-on developers on how to set up a performance testing environment.
- XUL School: Add-on Performance
- Tips for add-on developers to help them avoid impairing application performance.
- GPU performance
- Tips for profiling and improving performance when using a GPU.
View all pages tagged with "Performance"...
- about:memory is the easiest-to-use tool for measuring memory usage in Mozilla code, and is the best place to start. It also lets you do other memory-related operations like trigger GC and CC, dump GC & CC logs, and dump DMD reports. about:memory is built on top of Firefox's memory reporting infrastructure.
- DMD is a tool that identifies shortcomings in about:memory's measurements, and can also do multiple kinds of general heap profiling.
- areweslimyet.com (a.k.a. AWSY) is a memory usage and regression tracker.
- 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.
- Refcount tracing and balancing
- 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.
- GC and CC logs
- 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.
- Valgrind is a tool that detects various memory-related problems at runtime, including leaks. Valgrind is used as part of Mozilla's continuous integration testing, though the coverage is limited because Valgrind is slow.
- LeakSanitizer (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.
- Apple tools
- Apple provides some tools 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 bug 390944).
- Leak Gauge
- 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.
- 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.
See also the documentation on Leak-hunting strategies and tips.
- Profiling with the Built-in Profiler
- The built-in profiler is a good tool to start with.
- Profiling with Instruments
- How to use Apple's Instruments tool to profile Mozilla code.
- Profiling with Xperf
- How to use Microsoft's Xperf tool to profile Mozilla code.
- Profiling with Zoom
- Zoom is a profiler for Linux done by the people who made Shark
- Measuring performance using the PerfMeasurement.jsm code module
- Adding a new Telemetry probe
- Information on how to add a new measurement to the Telemetry performance-reporting system
- Profiling with Shark
- How to use Apple's Shark tool to profile Mozilla code.
- Investigating CSS Performance
- How to figure out why restyle is taking so long
Document Tags and Contributors