From 0ac84f3065f053a2edcab0dd55749c2f24e2a263 Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Wed, 6 Mar 2019 18:30:17 -0800 Subject: [PATCH] Added explicit Profiler goals to OVERVIEW --- OVERVIEW.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/OVERVIEW.md b/OVERVIEW.md index fe3dd90b00..d0709f9b97 100644 --- a/OVERVIEW.md +++ b/OVERVIEW.md @@ -165,9 +165,11 @@ while (index !== currentWeight) { ## Profiler -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.) +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: +* Minimizing bridge traffic. +* Efficiently serializing bridge messages. -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. +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. ### Profiling summary