distribution/registry/storage/driver
Josh Hawn e4dd3359cc Regulate filesystem driver to max of 100 calls
It's easily possible for a flood of requests to trigger thousands of
concurrent file accesses on the storage driver. Each file I/O call creates
a new OS thread that is not reaped by the Golang runtime. By limiting it
to only 100 at a time we can effectively bound the number of OS threads
in use by the storage driver.

Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn)

Signed-off-by: Tony Holdstock-Brown <tony@docker.com>
2016-04-26 14:44:13 -07:00
..
azure Update missing blob error checking with latest Azure API 2016-03-14 15:59:03 -07:00
base Regulate filesystem driver to max of 100 calls 2016-04-26 14:44:13 -07:00
factory Add documentation for how to register new StorageDrivers 2016-03-29 14:42:19 -07:00
filesystem Regulate filesystem driver to max of 100 calls 2016-04-26 14:44:13 -07:00
gcs Storagedriver: GCS: add chunksize parameter 2016-03-08 16:38:39 -08:00
inmemory Adds new storagedriver.FileWriter interface 2016-03-08 16:37:44 -08:00
middleware Adds new s3 driver using aws-sdk-go instead of goamz 2016-02-12 15:59:26 -08:00
oss Support FileWriter interface for OSS storage driver 2016-03-08 16:38:39 -08:00
s3-aws Merge pull request #1660 from jhaohai/cn-north-1-fix 2016-04-25 16:07:54 -07:00
s3-goamz Adds new storagedriver.FileWriter interface 2016-03-08 16:37:44 -08:00
swift detect outdated container listings during Stat() and getAllSegments() 2016-04-06 15:21:27 +02:00
testsuites StorageDriver: Testsuite: call Close before getting Size 2016-03-08 16:38:38 -08:00
fileinfo.go Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
storagedriver.go Remove the example 2016-03-29 14:42:28 -07:00