jasder
/
simdjson
1
0
Fork 0
Code Issues Pull Requests Releases 2 Wiki Activity

Update README.md

This commit is contained in:
Daniel Lemire 2019-01-18 12:00:18 -05:00 committed by GitHub
parent e2b8dcf966
commit 7536dff64b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -12,19 +12,6 @@ We can use a quarter or fewer instructions than a state-of-the-art parser like R
<img src="doc/gbps.png" width="90%"> <img src="doc/gbps.png" width="90%">
Next we present the time (in cycles per input byte) needed to fully parse a JSON file (with error checking) and to collect some statistics about the document (e.g., the number of integers), for some JSON files. For these tests, we use an Intel processor with a Skylake microarchitecture. All results are single-threaded. *Lower results are better.*
github_events.json:
<img src="doc/github_events.jsonparseandstat.png" width="50%">
twitter.json:
<img src="doc/twitter.jsonparseandstat.png" width="50%">
On a skylake processor, the parsing speeds (in GB/s) of various processors on the twitter.json file are as follows. On a skylake processor, the parsing speeds (in GB/s) of various processors on the twitter.json file are as follows.
| parser | GB/s | | parser | GB/s |
@ -98,7 +85,7 @@ See the "singleheader" repository for a single header version. See the included
file "amalgamation_demo.cpp" for usage. This requires no specific build system: just file "amalgamation_demo.cpp" for usage. This requires no specific build system: just
copy the files in your project in your include path. You can then include them quite simply: copy the files in your project in your include path. You can then include them quite simply:
``` ```C
#include <iostream> #include <iostream>
#include "simdjson.h" #include "simdjson.h"
#include "simdjson.cpp" #include "simdjson.cpp"