Commit 46c7541
committed
fix(settings): make DATA_UPLOAD_MAX_MEMORY_SIZE env-configurable
Previously hardcoded at 100 MB in base.py. In practice ADC workers
post ML result payloads for a full batch (detection coordinates +
classifications for tens of images) in a single POST, and those have
been observed in the 139–321 MB range on staging for the
global_moths_2024 pipeline — well above the 100 MB ceiling.
Raising the limit in code would be both premature (proper fix is
worker-side incremental posting, tracked in #1223) and environment-
specific (staging may need to tolerate today's payloads; production
may want a tighter ceiling to catch regressions). Making it an env
override lets each deployment tune without a code change and without
maintaining a hot-patch on the server.
Reads from ``DJANGO_DATA_UPLOAD_MAX_MEMORY_MB`` (integer, in MB).
Default stays at 100 MB so existing deployments see no change unless
they opt in.
Nginx's ``client_max_body_size`` still needs to be raised in lockstep
on the fronting proxy — that is independently configurable and lives
outside this repo.1 parent 8f8b177 commit 46c7541
1 file changed
Lines changed: 9 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
426 | 426 | | |
427 | 427 | | |
428 | 428 | | |
429 | | - | |
430 | | - | |
| 429 | + | |
| 430 | + | |
| 431 | + | |
| 432 | + | |
| 433 | + | |
| 434 | + | |
| 435 | + | |
| 436 | + | |
| 437 | + | |
431 | 438 | | |
432 | 439 | | |
433 | 440 | | |
| |||
0 commit comments