Benchmark: Markdown Performance Comparison 18

HTML Preparation code:

<script type="text/javascript" src="https://unpkg.com/marked@1.1.0/marked.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/commonmark@0.29.1/dist/commonmark.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/markdown-it@11.0.0/dist/markdown-it.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/remarkable@2.0.1/dist/remarkable.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/micromarkdown@0.3.0/dist/micromarkdown.min.js"></script>
<script type="text/javascript" src="https://unpkg.com/snarkdown@1.2.2/dist/snarkdown.umd.js"></script>

Script Preparation code:

var conv = {
  marked: marked,
  cm: new commonmark.HtmlRenderer(),
  mdit: markdownit({ html: true }),
  remarkable: new remarkable.Remarkable(),
  micromarkdown: window.micromarkdown,
  snarkdown: window.snarkdown,
};

var pars = {
  cm: new commonmark.Parser()
};

var md = "# The Static, Static Blog Generator\n\n### May 17th, 2014\n\nWe all like publishing our thoughts online - but why is it such a bother to run a CMS?\n\nManaging databases, updating software, and keeping track of our content often cuts into the most important activity: *expressing ourselves*.\n\nThe web makes it really easy to share our thoughts with millions of individuals from around the world. With it we are able to talk about the things we love.\n\nOnline publishing platform have a problem though - they require certain software to be installed on web servers in order to work. This often means running your own server or paying someone else who will setup the required parts for you.\n\nAfter you setup the system, constant updates are required to make sure that any bugs in the software you are running are patched immediately to prevent your site from being hacked. This often means having a recent backup of your database ready at all times.\n\n## Can't we simplify? \n\nBecause running websites and managing databases isn't always worth the effort, \"Static Content Generators\" like [Dr. jekyll](http://jekyllrb.com/) and [Mr. Hyde](http://hyde.github.io/) have begun to gain traction as people pre-build websites and then place the static HTML results onto their server. \n\nThis means the web server doesn't need to be configured with any special software or databases - it simply serves the generated static HTML files.\n\nHowever, you still have to install the generator and setup a \"build\" process of sorts after every article.\n\n## Meet Jr.\n\n\`Jr\` is a truly *static*, static content generator. All the processing of your files happens on the requesting client's computer as needed. The whole system is written in client-side JavaScript. This means:\n\n- minimal bandwidth requirements\n- better search engine indexing\n- awesome screen reader support\n- *zero* security vulnerabilities\n- and more!\n\nHowever, the neatest thing about \`Jr\` is that you don't have to configure, setup, or install _anything_! Simply download the files, create your articles, and upload everything to your server!\n\ndone.\n\n## GIT thee hence\n\nIf you want to be really awesome you can use \`Jr\` along with the ever useful *version-control* system [git](https://help.github.com/articles/set-up-git). This allows you to keep better track of changes insuring that you can always rollback your text to recover previous versions - very handy if you work with a team!\n\n## What About Markup?\n\nLike most systems, you can compose pages in \`Jr\` using the text-to-HTML format \"[markdown](http://daringfireball.net/projects/markdown/)\". You can also use plain HTML if you want.\n\n\n## Getting Started\n\n1. [Download](http://github.com/Xeoncross/Jr) \`Jr\`\n2. Make your \`[article-name].html\` files\n3. Paste the following code at the bottom of each page:  \n	<code>&lt;script src=&quot;jr.js&quot;&gt;&lt;/script&gt;</code>  \n\n\nOnce you have created your pages then simply upload the system to your website and enjoy.\n\n*P.S. Looking for a static social lifestream application? Checkout [MicroStream](https://github.com/Xeoncross/microstream).*\n\n![kitten](http://placekitten.com.s3.amazonaws.com/homepage-samples/408/287.jpg \"obligatory kitten image\")\n\n\n";

Tests:

Marked
conv.marked(md);
CommonMark
conv.cm.render(pars.cm.parse(md));
Markdown-it
conv.mdit.render(md);
Remarkable
conv.remarkable.render(md);
Micromarkdown
conv.micromarkdown.parse(md);
Snarkdown
conv.snarkdown(md);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Marked
CommonMark
Markdown-it
Remarkable
Micromarkdown
Snarkdown

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 26 days ago):

LLMs can make mistakes. Check important info.

Latest run results:

Run details: (Test run date: 2 years ago)

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0

Browser/OS: Firefox 104 on Linux

View result in a separate tab

Test name	Executions per second
Marked	2834.5 Ops/sec
CommonMark	2864.9 Ops/sec
Markdown-it	2118.4 Ops/sec
Remarkable	2402.1 Ops/sec
Micromarkdown	2416.0 Ops/sec
Snarkdown	4670.7 Ops/sec

Related benchmarks:

Markdown Performance Comparison 18 (version: 0)

A performance comparison of leading Javascript Markdown implementations.

Comparing performance of: Marked vs CommonMark vs Markdown-it vs Remarkable vs Micromarkdown vs Snarkdown

Created: 3 years ago by: Guest

Jump to the latest result

Marked

CommonMark

Markdown-it

Remarkable

Micromarkdown

Snarkdown

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 26 days ago):