Added explicit Profiler goals to OVERVIEW
Brian Vaughn committed
Mar 6, 2019 at 18:30 UTC
0ac84f3065f053a2edcab0dd55749c2f24e2a263
1 file changed
+4
-2
OVERVIEW.md
+4
-2
@@ -165,9 +165,11 @@ while (index !== currentWeight) {
165
166
## Profiler
167
168
-All profiling information is stored on the backend while profiling is in progress. (Avoiding sending traffic across the bridge reduces the performance overhead of running the profiler.)
168
+The Profiler UI is a powerful tool for identifying and fixing performance problems. The primary goal of the new profiler is to minimize the impact of running it (so that it doesn't interfere with the application beign profiled). This can be accomplished by:
169
+* Minimizing bridge traffic.
170
+* Efficiently serializing bridge messages.
171
170
-The backend push-notifies the frontend of when profiling starts ("_profilingStarted_") and stops ("_profilingStopped_"). All other profiling information is lazy and must be requested by the backend.
172
+All profiling information is stored on the backend. The backend push-notifies the frontend of when profiling starts ("_profilingStarted_") and stops ("_profilingStopped_"). All other profiling information is lazy and must be requested by the backend.
173
174
### Profiling summary
175