You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In experimenting with file transfers initiated by rclone/webdav I noticed that Reva runs out of memory very quickly with subsequent file transfers. The memory used for each transfer keeps adding up to the previously used memory until Reva runs out of memory, and then Reva is killed.
Here's the final part of the log until Reva is killed: mem-issue-reva-webdav-file-transfer.txt
It's the receiving Reva instance that takes up all the memory. In the experiments both source and destination Reva instances are running in docker containers as well as rclone.
Here's the result (docker stats) from a number of subsequent 600MB file transfers (4GB memory available for docker). Each subsequent transfer adds to the already used memory and in between transfers the memory does not gets freed up:
In experimenting with file transfers initiated by rclone/webdav I noticed that Reva runs out of memory very quickly with subsequent file transfers. The memory used for each transfer keeps adding up to the previously used memory until Reva runs out of memory, and then Reva is killed.
Here's the final part of the log until Reva is killed: mem-issue-reva-webdav-file-transfer.txt
It's the receiving Reva instance that takes up all the memory. In the experiments both source and destination Reva instances are running in docker containers as well as rclone.
Here's the result (docker stats) from a number of subsequent 600MB file transfers (4GB memory available for docker). Each subsequent transfer adds to the already used memory and in between transfers the memory does not gets freed up:
I am not experienced in the underlying implementation (TUS ?). Anyone?
The text was updated successfully, but these errors were encountered: