microsoft / microsoft/AzureStorageExplorer
Only limit local transfter speeds
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
If you set a Maximum transfer rate in settings it also rate limits copying objects within Azure when really I just want it to limit my local upload speed.
Describe the solution you'd like
Something that allows a max transfer rate just for local transfers. Maybe there is a valid use case for rate limiting copy inside Azure if you have lot of traffic?
The AzCopy command that gets run when copy and paste within storage explorer:
./azcopy.exe copy "https://xxxxxx.blob.core.windows.net/xxxxxx/1" "https://xxxxxx.blob.core.windows.net/xxxxx/2" --overwrite=prompt --recursive --cap-mbps 15 --s2s-preserve-access-tier=false;
Maybe you can just check if both src and dst are x.blob.core.windows.net and not apply limit etc.
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Storage Explorer turns the Maximum transfer rate setting into the shown AzCopy command for copy and paste. Compare local uploads with Azure-to-Azure transfers, then verify that the rate limit remains for local uploads while Azure-side copies no longer receive --cap-mbps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100