Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Chrome is slow, what do I do? | |
| 2 | |
| 3 ## How to file a bug | |
| 4 | |
| 5 * **File a bug.** To file a bug, please use | |
| 6 **[the speed bug template](https://bugs.chromium.org/p/chromium/issues/entry?tem plate=Speed%20Bug)**. | |
| 7 * **Attach a trace.** The best way to get performance data to developers is to include a trace, | |
| 8 so please [follow these instructions](https://www.chromium.org/developers/ho w-tos/trace-event-profiling-tool/recording-tracing-runs) | |
| 9 to record a trace and attach it to the bug. | |
| 10 * **(For Googlers) try TraceOnTap** the [TraceOnTap Extension](http://goto.goo gle.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.
| |
| 11 makes it easier to record traces and attach them to bugs. | |
| 12 | |
| 13 <!--- TODO: ## Bug SLO for perf bugs --> | |
| 14 | |
| 15 <!--- TODO: ## Bug Triage | |
| 16 ### High level | |
| 17 ### Best practices | |
| 18 ### 3 step approach to Speed Triage | |
| 19 ### Rotation Documentation | |
| 20 ### Bug Dashboards | |
| 21 ### Fixits | |
| 22 --> | |
| OLD | NEW |