-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Performance issues when including Autolinker #760
Comments
Thanks for reporting. Can you tell me which components (i.e. languages) are loaded? |
These languages: |
Thanks! It should be much better now. Please redownload with the link you provided and give it a try. If the problem persists, feel free to reopen! |
Thanks. The problem is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Evaluation of Prism.js is super slow when Autolinker is included. The following two images are showing the difference in evaluation time when Autolinker respectively is included and not included.
Both images are of a page that only includes Prism and but aren't using it.
This is the evaluation time is on a very fast desktop CPU. My Nexus 4 smartphone takes about 25 sec. for the same task.
This means that a page load takes 25 sec longer on my smartphone when Prism is included on the page, even though it isn't used.
The text was updated successfully, but these errors were encountered: