From a640cc26f402d661bee78377fa8cbb16ff2e4da2 Mon Sep 17 00:00:00 2001 From: Mikolaj Dadela Date: Mon, 17 Aug 2015 11:18:04 +0200 Subject: [PATCH] Updated the Performance tools doc page. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Now it’s possible to read the page from top to the bottom without asking oneself “Ok, but how do I get these measurements?” --- docs/10.9-perf.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/10.9-perf.md b/docs/10.9-perf.md index 33f257c2..735aac04 100644 --- a/docs/10.9-perf.md +++ b/docs/10.9-perf.md @@ -21,6 +21,8 @@ The `Perf` object documented here is exposed as `React.addons.Perf` when using t ### `Perf.start()` and `Perf.stop()` Start/stop the measurement. The React operations in-between are recorded for analyses below. Operations that took an insignificant amount of time are ignored. +After stopping, you will need `Perf.getLastMeasurements()` (described below) to get the measurements. + ### `Perf.printInclusive(measurements)` Prints the overall time taken. If no argument's passed, defaults to all the measurements from the last recording. This prints a nicely formatted table in the console, like so: