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

Performance review #32

Open
jacwright opened this issue Apr 25, 2018 · 3 comments
Open

Performance review #32

jacwright opened this issue Apr 25, 2018 · 3 comments
Labels
help wanted

Comments

@jacwright
Copy link
Member

We should review performance on large documents and see if there are bottlenecks or ways to improve it. I feel like Typewriter will be performant, but that is different than knowing. 🙂
@scarroll32
Copy link
Contributor

Great idea. Are there tools in the npm world for this?

@jacwright
Copy link
Member Author

I would just use Chrome's devtools. There are some great helps here https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/ to walk you through things you can do.

@jacwright
Copy link
Member Author

I've done a lot of testing with Quill, ProseMirror, and Typewriter and it feels like Typewriter is the smoothest ride with large documents. Numbers here would be great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jacwright @scarroll32