01729b18a5
This probably worsens performance in the common case, but it prevents runaway producers (see e.g. issue #36) from spending all their CPU copying around huge strings. It's also a small step towards a solution to issue #6, which will replace the output buffer with some sort of fancier queue anyway. This reduces a particular 40 second run of rsync to 1.5 seconds. |
||
---|---|---|
docs | ||
examples | ||
mitogen | ||
tests | ||
.gitignore | ||
README.md | ||
dev_requirements.txt | ||
preamble_size.py | ||
setup.py |
README.md
Running The Tests
Your computer should have an Internet connection, and the docker
command
line tool should be able to connect to a working Docker daemon (localhost or
elsewhere for OS X etc.) that can run new images.
The IP address of the Docker daemon must allow exposing ports from running containers, e.g. it should not be firewalled or port forwarded.
If in doubt, just install Docker on a Linux box in the default configuration and run the tests there.