-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture metrics using react-native-performance
#101
Conversation
It's optional as it's not need by Onyx It will only be used together with `captureMetrics: true` to benchmark Onyx
This looks good to me, but I'd like @marcaaron to take a look here since I know he's more involved in the performance metrics. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, but I spotted a few places where I think it couldn't hurt to add some additional context or clarifying code comments to make it easier to work on for the next person.
Since performance entries are created with `react-native-performance` they no longer contain `endTime`. End time is derived using `call.startTime` + `call.duration`
Addressed requested changes. Ready for review |
Details
We're already using
react-native-performance
in Expensify/AppUsing it here allows us to visualize Onyx measures in Flipper
Related Issues
Expensify/App#4656 (comment)
Automated Tests
Covered by existing tests
Linked PRs