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..0003608b5d9814e0144f6a5dad784db189c25d28 |
--- /dev/null |
+++ b/docs/speed/help_improve_performance.md |
@@ -0,0 +1,23 @@ |
+# 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. |
+ * **Try TraceOnTap** the [TraceOnTap Extension](http://goto.google.com/traceontap) |
+ makes it easier to record traces and attach them to bugs. |
+ [Source code](https://github.com/catapult-project/catapult/tree/master/experimental/trace_on_tap) |
+ |
+<!--- TODO: ## Bug SLO for perf bugs --> |
+ |
+<!--- TODO: ## Bug Triage |
+### High level |
+### Best practices |
+### 3 step approach to Speed Triage |
+### Rotation Documentation |
+### Bug Dashboards |
+### Fixits |
+--> |