Investigate memory usage in PHP during digital object upload
|Google Code Legacy ID:||Tested version:||2.5, 2.6|
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.