Confirmed users
328
edits
(Move latency tools back over to Performance:Tools) |
(→Tools) |
||
Line 98: | Line 98: | ||
== Tools == | == Tools == | ||
Mozilla has a ton of great tools already available for analyzing performance, including | Mozilla has a ton of great tools already available for analyzing performance, including some I haven't uncovered yet. I'm updating [[Performance:Tools]] with everything I encounter. | ||
=== Audiences === | === Audiences === | ||
The audience determines whether a tool can be enabled via a conditional compilation directive, or whether it needs to be available in a release build. It also gives guidance as to whether a platform-specific tool is acceptable (eg dtrace). | |||
* Mozilla platform developers | * Mozilla platform developers | ||
* Mozilla application developers | ** Can be platform-dependent and require different build options. | ||
* | ** Nice if they can be fully automated and added to buildbot | ||
* Mozilla application developers (Firefox, Thunderbird, etc.) | |||
** Similar constraints as for "Mozilla platform developers" | |||
* Add-on authors | * Add-on authors | ||
** Platform dependence dramatically limits scope | |||
** Different build options are problematic, but in some cases will be ok. | |||
* Web application authors | |||
** Pretty much needs to be platform independent | |||
** Different build options are problematic, but in some cases will be ok. | |||
* General web developers | |||
** Pretty much needs to be platform independent | |||
** Must be available in release build, though enabling via config options or as an add-on is ok | |||
=== Tool Ideas === | === Tool Ideas === |