Files
react-native/Libraries
Ruslan Shestopalyuk bc56f66b8d Implement Performance.getEntries* W3C extension for Performance Timeline API (#36314)
Summary:
Pull Request resolved: https://github.com/facebook/react-native/pull/36314

## Changelog:

[Internal] - Added support for W3C Performance API extension (Performance,getEntries*)

See [here for the details](https://www.w3.org/TR/performance-timeline/#extensions-to-the-performance-interface).

This only supports `mark` and `measure` performance entry types (not `events`, as those are not supported by browsers either, they recommend using the `PerformanceObserver` API instead).

From the implementation perspective, we already maintained persistent buffer for `mark` entry types, which was required in order to look up measures.

The buffer is circular, limited to 1K entries by default.

I basically mimic the same behavior for `measure` entry types as well, since it's the simplest way of doing it at this point,

If we happen to want adding some other entry types that would be available via `Performance.getEntries*` API in the future, we may want to iterate on the internal data structures representation inside `PerformanceEntryReporter`, but for now I believe this approach should work just fine, and whatever changes we may want to do will be purely internal implementation detail.

Reviewed By: rubennorte

Differential Revision: D43625488

fbshipit-source-id: dd315b3f8488e910749a8e2a4158246e94d76f99
2023-03-01 04:14:51 -08:00
..
2022-09-30 14:28:48 -07:00
2023-02-28 10:23:36 -08:00
2022-09-30 14:28:48 -07:00
2023-01-23 07:38:48 -08:00
2022-09-30 14:28:48 -07:00
2023-02-28 10:23:36 -08:00
2023-02-28 10:23:36 -08:00
2022-09-30 14:28:48 -07:00
2023-02-28 15:17:21 -08:00
2023-01-03 18:09:06 -08:00
2023-02-28 10:23:36 -08:00
2022-09-30 14:28:48 -07:00
2023-02-28 10:23:36 -08:00
2022-12-06 19:34:14 -08:00
2023-02-28 10:23:36 -08:00
2022-11-02 14:58:37 -07:00
2023-02-28 10:23:36 -08:00
2023-02-28 10:23:36 -08:00
2023-01-19 14:04:23 -08:00