Skip to content
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.

Sign up for GitHub

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

Jump to bottom

React-native: why JS bridge is the performance bottleneck #19678

Closed
marialovesbeans opened this issue Jun 12, 2018 · 2 comments
Closed

React-native: why JS bridge is the performance bottleneck #19678

marialovesbeans opened this issue Jun 12, 2018 · 2 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot. Type: Invalid This issue does not belong here. Applying this label will cause issue to be closed.

Comments

@marialovesbeans
Copy link

People say we should minimize passing data via JS bridge. I want to know what exactly makes JS bridge slow? Serializing & deserializing should be fast, non? (aka can be done under 16ms)

Example of such claim made by Wix CTO: https://youtube.com/watch?v=OmiXlJ4ZzAo
@react-native-bot
Copy link
Collaborator

It looks like your issue may be incomplete. Are all the fields required by the Issue Template filled out?

If you believe your issue contains all the relevant information, let us know in order to have a maintainer remove the No Template label.

@timwangdev timwangdev added the Type: Invalid This issue does not belong here. Applying this label will cause issue to be closed. label Jun 13, 2018
@react-native-bot
Copy link
Collaborator

We use GitHub Issues exclusively for tracking bugs in React Native. See the React Native Community Support page for a list of places where you may ask for help.

@react-native-bot react-native-bot added the Ran Commands One of our bots successfully processed a command. label Jun 13, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Jun 13, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jun 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot. Type: Invalid This issue does not belong here. Applying this label will cause issue to be closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@timwangdev @react-native-bot @marialovesbeans