mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Xin Chen
c1023c73b0
Summary: This diff adds the `performance.reactNativeStartupTiming` API to the performance global object for RN. This property does not exist in web, and we are free to make up our own list of properties in the startup metrics to track RN app startup process. In our case, we have the following six properties to begin with (we may extend and add more to this list in the future): ``` - `(start|end)Time`: The time ‘zero’ for the startup timing and the end of app startup. RN has no knowledge of app start time, which will be provided by the platform. The `endTime` will be the time when the first JS bundle finishes executing (Note that RN supports multiple JS bundles, which can be loaded async) - `executeJavaScriptBundleEntryPoint(Start|End)`: The time for RN to execute the JS entry point (and finish all sync job) ``` Changelog: [General][Added] - Add new JS performance API to support getting RN app startup timings Reviewed By: rshest Differential Revision: D43326564 fbshipit-source-id: 7b4c7cae70ff64ba1714a1630cd5e183df6c06b0
77 lines
2.4 KiB
C++
77 lines
2.4 KiB
C++
/*
|
|
* Copyright (c) Meta Platforms, Inc. and affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <FBReactNativeSpec/FBReactNativeSpecJSI.h>
|
|
#include <memory>
|
|
#include <string>
|
|
|
|
#include "NativePerformanceObserver.h"
|
|
|
|
namespace facebook::react {
|
|
class PerformanceEntryReporter;
|
|
|
|
#pragma mark - Structs
|
|
|
|
using ReactNativeStartupTiming =
|
|
NativePerformanceCxxBaseReactNativeStartupTiming<
|
|
int32_t, // Start time of the RN app startup process
|
|
int32_t, // End time of the RN app startup process
|
|
int32_t, // Start time that RN app execute the JS bundle
|
|
int32_t // End time that RN app execute the JS bundle
|
|
>;
|
|
|
|
template <>
|
|
struct Bridging<ReactNativeStartupTiming>
|
|
: NativePerformanceCxxBaseReactNativeStartupTimingBridging<
|
|
int32_t,
|
|
int32_t,
|
|
int32_t,
|
|
int32_t> {};
|
|
|
|
#pragma mark - implementation
|
|
|
|
class NativePerformance : public NativePerformanceCxxSpec<NativePerformance>,
|
|
std::enable_shared_from_this<NativePerformance> {
|
|
public:
|
|
NativePerformance(std::shared_ptr<CallInvoker> jsInvoker);
|
|
|
|
void
|
|
mark(jsi::Runtime &rt, std::string name, double startTime, double duration);
|
|
|
|
void measure(
|
|
jsi::Runtime &rt,
|
|
std::string name,
|
|
double startTime,
|
|
double endTime,
|
|
std::optional<double> duration,
|
|
std::optional<std::string> startMark,
|
|
std::optional<std::string> endMark);
|
|
|
|
// To align with web API, we will make sure to return three properties
|
|
// (jsHeapSizeLimit, totalJSHeapSize, usedJSHeapSize) + anything needed from
|
|
// the VM side.
|
|
// `jsHeapSizeLimit`: The maximum size of the heap, in bytes, that
|
|
// is available to the context.
|
|
// `totalJSHeapSize`: The total allocated heap size, in bytes.
|
|
// `usedJSHeapSize`: The currently active segment of JS heap, in
|
|
// bytes.
|
|
//
|
|
// Note that we use int64_t here and it's ok to lose precision in JS doubles
|
|
// for heap size information, as double's 2^53 sig bytes is large enough.
|
|
std::unordered_map<std::string, double> getSimpleMemoryInfo(jsi::Runtime &rt);
|
|
|
|
// Collect and return the RN app startup timing information for performance
|
|
// tracking.
|
|
ReactNativeStartupTiming getReactNativeStartupTiming(jsi::Runtime &rt);
|
|
|
|
private:
|
|
};
|
|
|
|
} // namespace facebook::react
|