Skip to content
Browse files

Update performance numbers

This clearly shows that on this dataset, decoding is about 33%
faster than the previous release, while encoding is about twice as
fast. Nice!
  • Loading branch information...
1 parent 0d1d835 commit 9636fda8b6a02a3b4b8df3edc1c681c84f23784a @bos committed Jan 8, 2014
Showing with 13 additions and 13 deletions.
  1. +13 −13 aeson.cabal
View
26 aeson.cabal
@@ -25,37 +25,37 @@ description:
running 64-bit GHC 7.6.3, for mostly-English tweets from Twitter's
JSON search API:
.
- * 0.8 KB: 27992 msg\/sec (22.8 MB\/sec)
+ * 0.8 KB: 34124 msg\/sec (27.8 MB\/sec)
.
- * 6.4 KB: 5604 msg\/sec (35.2 MB\/sec)
+ * 6.4 KB: 6833 msg\/sec (43.0 MB\/sec)
.
- * 11.8 KB: 2682 msg\/sec (30.9 MB\/sec)
+ * 11.8 KB: 3410 msg\/sec (39.2 MB\/sec)
.
- * 31.2 KB: 836 msg\/sec (25.5 MB\/sec)
+ * 31.2 KB: 1157 msg\/sec (35.3 MB\/sec)
.
- * 61.5 KB: 441 msg\/sec (26.5 MB\/sec)
+ * 61.5 KB: 542 msg\/sec (32.5 MB\/sec)
.
Handling heavily-escaped text is a little more work. Here is
parsing performance with Japanese tweets, where much of the text
is entirely Unicode-escaped.
.
- * 14.6 KB: 1823 msg\/sec (26.1 MB\/sec)
+ * 14.6 KB: 2101 msg\/sec (30.0 MB\/sec)
.
- * 44.1 KB: 550 msg\/sec (23.7 MB\/sec)
+ * 44.1 KB: 667 msg\/sec (28.7 MB\/sec)
.
- * 82.9 KB: 278 msg\/sec (22.5 MB\/sec)
+ * 82.9 KB: 360 msg\/sec (29.2 MB\/sec)
.
Encoding performance on the same machine and data:
.
- * English, 0.8 KB: 54236 msg\/sec (44.2 MB\/sec)
+ * English, 0.8 KB: 109697 msg\/sec (89.3 MB\/sec)
.
- * English, 6.4 KB: 10210 msg\/sec (64.2 MB\/sec)
+ * English, 6.4 KB: 18517 msg\/sec (116.4 MB\/sec)
.
- * Engish, 61.5 KB: 1130 msg\/sec (67.9 MB\/sec)
+ * Engish, 61.5 KB: 1963 msg\/sec (118.0 MB\/sec)
.
- * Japanese, 14.6 KB: 6509 msg\/sec (93.0 MB\/sec)
+ * Japanese, 14.6 KB: 12140 msg\/sec (173.5 MB\/sec)
.
- * Japanese, 44.1 KB: 2078 msg\/sec (89.5 MB\/sec)
+ * Japanese, 44.1 KB: 3980 msg\/sec (171.3 MB\/sec)
.
(A note on naming: in Greek mythology, Aeson was the father of Jason.)

0 comments on commit 9636fda

Please sign in to comment.
Something went wrong with that request. Please try again.