' >> out/index.html
-python -m markdown -x markdown.extensions.fenced_code REPORT.md >> out/index.html
-echo '
' >> out/index.html
-echo '' >> out/index.html
-echo '' >> out/index.html
diff --git a/data.py b/data.py
deleted file mode 100644
index ff11bab..0000000
--- a/data.py
+++ /dev/null
@@ -1,17 +0,0 @@
-
-class ChildTestObject(object):
- def __init__(self, multiplier=None):
- self.w = 1000 * multiplier if multiplier else 100
- self.x = 20 * multiplier if multiplier else 20
- self.y = 'hello' * multiplier if multiplier else 'hello'
- self.z = 10 * multiplier if multiplier else 10
-
-
-class ParentTestObject(object):
- def __init__(self):
- self.foo = 'bar'
- self.sub = ChildTestObject()
- self.subs = [ChildTestObject(i) for i in range(10)]
-
- def bar(self):
- return 5
diff --git a/deploy-key.enc b/deploy-key.enc
deleted file mode 100644
index 4c226d2..0000000
Binary files a/deploy-key.enc and /dev/null differ
diff --git a/deploy.sh b/deploy.sh
deleted file mode 100755
index 40dbb59..0000000
--- a/deploy.sh
+++ /dev/null
@@ -1,60 +0,0 @@
-#! /bin/bash
-set -ex # Exit with nonzero exit code if anything fails
-
-SOURCE_BRANCH="master"
-TARGET_BRANCH="gh-pages"
-
-function doCompile {
- ./create_report.sh
-}
-
-# Pull requests and commits to other branches shouldn't try to deploy, just build to verify
-if [ "$TRAVIS_PULL_REQUEST" != "false" -o "$TRAVIS_BRANCH" != "$SOURCE_BRANCH" ]; then
- echo "Skipping deploy; just doing a build."
- doCompile
- exit 0
-fi
-
-# Save some useful information
-REPO=`git config remote.origin.url`
-SSH_REPO=${REPO/https:\/\/github.com\//git@github.com:}
-SHA=`git rev-parse --verify HEAD`
-
-# Clone the existing gh-pages for this repo into out/
-# Create a new empty branch if gh-pages doesn't exist yet (should only happen on first deply)
-git clone $REPO out
-cd out
-git checkout $TARGET_BRANCH || git checkout --orphan $TARGET_BRANCH
-cd ..
-
-# Clean out existing contents
-rm -rf out/**/* || exit 0
-
-# Run our compile script
-doCompile
-
-# Now let's go have some fun with the cloned repo
-cd out
-git config user.name "Travis CI"
-git config user.email "$COMMIT_AUTHOR_EMAIL"
-
-# Commit the "changes", i.e. the new version.
-# The delta will show diffs between new and old versions.
-git add .
-git commit -m "Deploy to GitHub Pages: ${SHA}"
-
-# Get the deploy key by using Travis's stored variables to decrypt deploy_key.enc
-ENCRYPTED_KEY_VAR="encrypted_${ENCRYPTION_LABEL}_key"
-ENCRYPTED_IV_VAR="encrypted_${ENCRYPTION_LABEL}_iv"
-ENCRYPTED_KEY=${!ENCRYPTED_KEY_VAR}
-ENCRYPTED_IV=${!ENCRYPTED_IV_VAR}
-openssl aes-256-cbc -K $ENCRYPTED_KEY -iv $ENCRYPTED_IV -in ../deploy-key.enc -out deploy-key -d
-chmod 600 deploy-key
-eval `ssh-agent -s`
-ssh-add deploy-key
-
-rm -fR __pycache__
-rm -fR subjects/__pycache__
-
-# Now that we're all set up, we can push.
-git push $SSH_REPO $TARGET_BRANCH
diff --git a/docker-compose.yml b/docker-compose.yml
deleted file mode 100644
index 21ff9bc..0000000
--- a/docker-compose.yml
+++ /dev/null
@@ -1,6 +0,0 @@
-tests:
- build: .
- command: python benchmark.py
- dockerfile: Dockerfile
- volumes:
- - .:/opt/code
diff --git a/disscussion.md b/index.html
similarity index 56%
rename from disscussion.md
rename to index.html
index 1494574..ef32fb9 100644
--- a/disscussion.md
+++ b/index.html
@@ -1,11 +1,60 @@
-## The Benchmark
-
-Each framework is asked to serialize a list of 2 objects a 1000 times, and then 1 object a 1000 times.
-
-This is the current object that is being serialized.
-
-```python
-class ChildTestObject(object):
+
+
+
+
Python Serialization Benchmark
+
This repository maintains a set of benchmarks for python serialization frameworks.
+
You can find the latest benchmarks on this page.
+
Currently the following projects are benchmarked.
+
+
Along with a baseline custom function that doesn't use a framework.
+
Running the test suite
+
A Docker container is bundled with the repository which you can use to run the benchmarks. Firstly make sure you have Docker installed.
+
+-
+
Install Docker
+
+-
+
Build the container $ docker-compose build
+
+-
+
Run the tests. $ docker-compose run --rm tests
+
+
+
Library Many Objects (seconds) One Object (seconds) Relative
+--------------------- ------------------------ ---------------------- ----------
+serpyco 0.00796103 0.00404453 1
+Custom 0.009902 0.00483012 1.22711
+lima 0.012424 0.00625205 1.55562
+Pickle 0.0180094 0.0179398 2.99438
+serpy 0.0356748 0.0189779 4.55228
+Strainer 0.0529356 0.0261641 6.58858
+Toasted Marshmallow 0.0865085 0.0465157 11.0802
+Colander 0.238111 0.116309 29.5214
+Lollipop 0.32454 0.156491 40.0673
+Avro 0.442609 0.220602 55.2419
+Marshmallow 0.496984 0.242603 61.6036
+kim 0.616623 0.307922 77.0097
+Django REST Framework 0.761326 0.527056 107.315
+
+
The Benchmark
+
Each framework is asked to serialize a list of 2 objects a 1000 times, and then 1 object a 1000 times.
+
This is the current object that is being serialized.
+
class ChildTestObject(object):
def __init__(self, multiplier=None):
self.w = 1000 * multiplier if multiplier else 100
self.x = 20 * multiplier if multiplier else 20
@@ -23,12 +72,9 @@
return 5
benchmark_object = ParentTestObject()
-```
-
-## Discussion
-
-Serialization from python objects to JSON, XML, or other transmission formats is a common task for many web related projects. In order to fill that need a number of frameworks have arised. While their aims are similar, they don't all share the same attributes. Here are how some of the features comapre.
-
+
+
Discussion
+
Serialization from python objects to JSON, XML, or other transmission formats is a common task for many web related projects. In order to fill that need a number of frameworks have arised. While their aims are similar, they don't all share the same attributes. Here are how some of the features comapre.
-* **Serialization**: Does the framework provide a way of serializing python objects to simple datastructures
-* **Encoding**: Does the framework provide a way of encoding data into a wire format
-* **Deserialization**: Does the framework provide a way of deserializing simple data structures into complex data structures
-* **Validation**: Does the framework provide a way of validating datastructures, and reprorting error conditions
-* **Part of Framework**: Is serialization apart of a larger framework
+
+- Serialization: Does the framework provide a way of serializing python objects to simple datastructures
+- Encoding: Does the framework provide a way of encoding data into a wire format
+- Deserialization: Does the framework provide a way of deserializing simple data structures into complex data structures
+- Validation: Does the framework provide a way of validating datastructures, and reprorting error conditions
+- Part of Framework: Is serialization apart of a larger framework
+