Add remarkable benchmark #19
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was interested in seeing how
markdown-wasmcompares toremarkable, which was made to improvemarked- not only to improve speed but also add plugins. Their benchmarks say over 3 times speed increase overmarked(which if accurate would mean it's faster thanmarkdown-wasm), in reality it's less than 2 times on average.This pull request adds
remarkableto the benchmark suite (with their default settings) and updates rendered images to include my results. You likely want to run it on your macbook to have the results from your macbook as stated in README.I have 3.5 GHz AMD Ryzen 3 desktop, 16GB RAM running Manjaro 5.10