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
Very high RAM usage (~12GB) during a copy procedure from one Azure Storage Account to another.
Size is around ~7M blobs / ~500GB
After around 40 minutes of copying the azcopy process and parent process (Windows Terminal) crashed.
During the whole time the client had also high disk i/o (probably writing to the pagefile.sys)
How can we reproduce the problem in the simplest way?
Copy large amount of data from one azure storage account to another.
Have you found a mitigation/solution?
Used version azcopy 10.24.0 instead, which stayed at ~200MB of RAM usage the whole way.
The text was updated successfully, but these errors were encountered:
Which version of the AzCopy was used?
azcopy version 10.27.1
Which platform are you using? (ex: Windows, Mac, Linux)
OS:
Windows 11 24H2
RAM:
16GB
What command did you run?
azcopy copy $SrcContainer$SrcSasKey $DstContainer$DstSasKey --recursive --log-level "ERROR"
copy https://acc1.blob.core.windows.net/container/?se=2025-01-03t09%3A40%3A19z&sig=-REDACTED-&sp=rl&srt=sco&ss=b&sv=2023-08-03 https://acc2.blob.core.windows.net/container/?se=2025-01-03t09%3A40%3A18z&sig=-REDACTED-&sp=rw&srt=sco&ss=b&sv=2023-08-03 --recursive --log-level ERROR
What problem was encountered?
Very high RAM usage (~12GB) during a copy procedure from one Azure Storage Account to another.
Size is around ~7M blobs / ~500GB
After around 40 minutes of copying the azcopy process and parent process (Windows Terminal) crashed.
During the whole time the client had also high disk i/o (probably writing to the pagefile.sys)
How can we reproduce the problem in the simplest way?
Copy large amount of data from one azure storage account to another.
Have you found a mitigation/solution?
Used version azcopy 10.24.0 instead, which stayed at ~200MB of RAM usage the whole way.
The text was updated successfully, but these errors were encountered: