cmark

My personal build of CMark ✏️

Commit: 18c32c79bad08359c5590a93c818be51f1f63021
Parent: 39b40151afa1af92c2d585c86930393be7e8ac73
Author: John MacFarlane <jgm@berkeley.edu>
Date: Thu, 11 Jun 2015 10:17:25 -0700

Updated benchmarks.md.

Removed sundown, because the reading was anomalous.

This commit in hoedown caused the speed difference btw sundown and hoedown that I was measuring before (on 32 bit machines):

https://github.com/hoedown/hoedown/commit/ca829ff83580ed52cc56c09a67c80119026bae20

As Nick Wellnhofer explains: "The commit removes a rather arbitrary limit of 16MB for buffers. Your benchmark input probably results in an buffer larger than 16MB. It also seems that hoedown didn't check error returns thoroughly at the time of the commit. This basically means that large input files ould produce any kind of random behavior before that commit, and that any benchmark that results in a too large buffer can't be relied on."

Diffstat

1 file changed, 1 insertion, 2 deletions

Status	File Name	N° Changes	Insertions	Deletions
Modified	benchmarks.md	3	1	2

diff --git a/benchmarks.md b/benchmarks.md
@@ -14,8 +14,7 @@ Some benchmarks, run on an ancient Thinkpad running Intel Core 2 Duo at 2GHz.
 | marked            |    1.94    |
 | **commonmark.js** |    1.93    |
 | discount          |    1.86    |
-| **cmark**         |    0.35    |
-| sundown           |    0.34    |
+| **cmark**         |    0.32    |
 | hoedown           |    0.21    |
 
 To run these benchmarks, use `make bench PROG=/path/to/program`.