cmark

My personal build of CMark ✏️

Commit: ee90975c1800f531f9a4490ac195e39b480a01c1
Parent: eb0576780eff57422e4d50a8aacfb1514e4299cd
Author: John MacFarlane <jgm@berkeley.edu>
Date: Tue, 4 Nov 2014 21:51:04 -0800

Clarify benchmark conditions in README.md.

Closes #183.

Diffstat

1 file changed, 12 insertions, 8 deletions

Status	File Name	N° Changes	Insertions	Deletions
Modified	README.md	20	12	8

diff --git a/README.md b/README.md
@@ -17,14 +17,18 @@ developers, since `scanners.c` can be provided in a released source
 tarball.)
 
 The parser is very fast, on par with
-[sundown](https://github.com/vmg/sundown).  Some benchmarks:
-
-|Implementation | Time to parse a 500K book |
-|---------------|---------------------------|
-| Markdown.pl   | 3.99s                     |
-| discount      | 0.089s                    |
-| sundown       | 0.015s                    |
-| cmark         | 0.019s                    |
+[sundown](https://github.com/vmg/sundown).  Some benchmarks (on
+a 1.6 GHz Intel Core i5, 4 GB RAM, mesaured using `time`, and parsing a
+~500K book, the English version of [*Pro
+Git*](https://github.com/progit/progit/tree/master/en) by
+Scott Chacon and Ben Straub):
+
+|Implementation | Time  |
+|---------------|-------|
+| Markdown.pl   | 3.990s|
+| discount      | 0.089s|
+| sundown       | 0.015s|
+| cmark         | 0.019s|
 
     Usage:   cmark [FILE*]
     Options: --help, -h    Print usage information