985d3bd404
These two cases did not actually read the same content with each iteration of the benchmark. After the first read, the buffer was consumed. This patch corrects this by using a bytes.Reader and seeking to the beginning of the buffer at the beginning of each iteration. Unfortunately, this benchmark was not actually as fast as we believed. But the new results do bring its results closer to those of the other benchmarks. Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn) |
||
|---|---|---|
| archive | ||
| broadcastwriter | ||
| chrootarchive | ||
| devicemapper | ||
| fileutils | ||
| graphdb | ||
| httputils | ||
| ioutils | ||
| iptables | ||
| jsonlog | ||
| listenbuffer | ||
| mflag | ||
| mount | ||
| namesgenerator | ||
| networkfs | ||
| parsers | ||
| pools | ||
| promise | ||
| proxy | ||
| reexec | ||
| signal | ||
| stdcopy | ||
| symlink | ||
| sysinfo | ||
| system | ||
| systemd | ||
| tailfile | ||
| tarsum | ||
| term | ||
| testutils | ||
| timeutils | ||
| truncindex | ||
| units | ||
| urlutil | ||
| version | ||
| README.md | ||
pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.
Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.
The directory pkg is named after the same directory in the camlistore project. Since Brad is a core
Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!
Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!