Bug #13236
Investigate memory usage in PHP during digital object upload
| Status: | New | Start date: | 01/09/2020 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - | |||
| Google Code Legacy ID: | Tested version: | 2.5, 2.6 | ||
| Sponsored: | No | Requires documentation: |
Description
It seems that when a digital object is uploaded (regardless of method, UI vs CLI), AtoM is loading the entire bitstream into memory. This can exhaust available memory with large upload attempts (especially when also factoring swap space memory), as seen in the following recent user forum post:
This issue is to track this behavior, and so we can investigate the rationale, and possible alternatives or improvements so that uploading digital objects is not so resource-intensive.
Related issues
History
#1 Updated by José Raddaoui Marín about 1 month ago
- Related to Bug #13245: Checksum validation fails when importing large digital objects added
#2 Updated by José Raddaoui Marín about 1 month ago
Work in progress PR: https://github.com/artefactual/atom/pull/1028