How do you shutdown TransferManager. about azure-storage-net-data-movement HOT 14 CLOSED

May I suggest that constant 30-40% CPU usage while idle suggest something wrong with the logic/operation, not a matter of shutdown or not. Unless of course it has useful things to do while idle and not shutdown.

from azure-storage-net-data-movement.

@SebastianAchatz We've got a change from a contributor. We are considering to take the change. The change has already passed our functional test, and we are also running Perf test against.

Thanks
Emma

from azure-storage-net-data-movement.

TransferManager cannot be shutdown or stopped for now. We are also considering to do some change to let customers be able to shut it down. I'll update you when add this function.

from azure-storage-net-data-movement.

Is it safe to use this library on a website?

from azure-storage-net-data-movement.

@smagnetize What kind of concern do you have? Are you worried about security or robust?

from azure-storage-net-data-movement.

Hey. I'm having the same problems as @sgmoore. TransferScheduler and FillInQueue are using up to 30-40% CPU on certain computers, even while idle. On other computers it's not as much of an issue (using 1-2% cpu while idle), even though it's the same methods that uses the most CPU. Shutting these down would be solving some (but not all) of the problems.

from azure-storage-net-data-movement.

@bamo-powel This is a scenario we should consider. We'll put this in our backlog.

from azure-storage-net-data-movement.

I'm also seeing this use an excessive amount of CPU when idle, TransferScheduler needs to relax when it has no work to do or there needs to be some mechanism to shut it down from TransferManager

from azure-storage-net-data-movement.

This is a massive showstopper for me using the library in a project. Any progress on this?

from azure-storage-net-data-movement.

@EmmaZhu Do you have any idea on when a decision might be made to release a fix?

from azure-storage-net-data-movement.

@sgmoore @SebastianAchatz
With latest version of 0.8.0 and 0.8.1, I've written a small test app to test scenario like following:

1. Upload a directory to blob with TransferManager
2. Wait

In the second phase, the CPU usage changes from 0~1%. Would you like to have a try?

from azure-storage-net-data-movement.

Hi, we have the same problem.

I'm using TransferManager for copying blobs and containers (TransferManager.CopyDirectoryAsync, TransferManager.CopyAsync). Even when nothing is trasfered for hours, it still uses about 10-15% CPU.
According to your last comment I updated library to version 0.8.1, but it doesn't help.

from azure-storage-net-data-movement.

Isn't this fixed as of https://github.com/Azure/azure-storage-net-data-movement/releases/tag/v1.1.0 ?

Fixed an issue of CPU is still in using when there's nothing being transferred in DataMovement Library

Also, the PSH issue referring back to this issue has been marked as closed.

from azure-storage-net-data-movement.

Thanks for the remind!
Close as it's fixed.

from azure-storage-net-data-movement.