fix: fence concurrent ZIP archive builds
This commit is contained in:
@@ -27,6 +27,11 @@ WORKER_TASK_CONCURRENCY=4
|
||||
WORKER_CONCURRENCY=2
|
||||
IMAGE_PROCESSING_CONCURRENCY=4
|
||||
|
||||
# Two concurrent 2 GiB ZIP builds require roughly 8 GiB of temporary disk.
|
||||
ZIP_BUILD_CONCURRENCY=2
|
||||
ZIP_MAX_ENTRIES=200
|
||||
ZIP_MAX_UNCOMPRESSED_BYTES=2147483648
|
||||
|
||||
# Resource ceilings tuned for an 8-core / 16 GB application host.
|
||||
POSTGRES_MEMORY_LIMIT=2g
|
||||
REDIS_MEMORY_LIMIT=1g
|
||||
|
||||
@@ -13,6 +13,9 @@ x-imageforge-environment: &imageforge-environment
|
||||
WORKER_TASK_CONCURRENCY: ${WORKER_TASK_CONCURRENCY:-4}
|
||||
WORKER_CONCURRENCY: ${WORKER_CONCURRENCY:-2}
|
||||
IMAGE_PROCESSING_CONCURRENCY: ${IMAGE_PROCESSING_CONCURRENCY:-2}
|
||||
ZIP_BUILD_CONCURRENCY: ${ZIP_BUILD_CONCURRENCY:-2}
|
||||
ZIP_MAX_ENTRIES: ${ZIP_MAX_ENTRIES:-200}
|
||||
ZIP_MAX_UNCOMPRESSED_BYTES: ${ZIP_MAX_UNCOMPRESSED_BYTES:-2147483648}
|
||||
ALLOW_ANONYMOUS_UPLOAD: ${ALLOW_ANONYMOUS_UPLOAD:-true}
|
||||
ANON_MAX_FILE_SIZE_MB: ${ANON_MAX_FILE_SIZE_MB:-5}
|
||||
ANON_MAX_FILES_PER_BATCH: ${ANON_MAX_FILES_PER_BATCH:-5}
|
||||
|
||||
Reference in New Issue
Block a user