Chromium Code Reviews| Index: docs/speed/help_improve_performance.md |
| diff --git a/docs/speed/help_improve_performance.md b/docs/speed/help_improve_performance.md |
| new file mode 100644 |
| index 0000000000000000000000000000000000000000..c7f4412b9ed7e30cab9e6213748bc07d922e069c |
| --- /dev/null |
| +++ b/docs/speed/help_improve_performance.md |
| @@ -0,0 +1,22 @@ |
| +# Chrome is slow, what do I do? |
| + |
| +## How to file a bug |
| + |
| + * **File a bug.** To file a bug, please use |
| +**[the speed bug template](https://bugs.chromium.org/p/chromium/issues/entry?template=Speed%20Bug)**. |
| + * **Attach a trace.** The best way to get performance data to developers is to include a trace, |
| + so please [follow these instructions](https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs) |
| + to record a trace and attach it to the bug. |
| + * **(For Googlers) try TraceOnTap** the [TraceOnTap Extension](http://goto.google.com/traceontap) |
|
benhenry
2017/06/16 22:01:25
This is not restricted to Googlers, so we should m
sullivan
2017/06/16 22:34:25
Thanks! Done.
|
| + makes it easier to record traces and attach them to bugs. |
| + |
| +<!--- TODO: ## Bug SLO for perf bugs --> |
| + |
| +<!--- TODO: ## Bug Triage |
| +### High level |
| +### Best practices |
| +### 3 step approach to Speed Triage |
| +### Rotation Documentation |
| +### Bug Dashboards |
| +### Fixits |
| +--> |