Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Speedsummary don't get updated when downloading file/blob under 32MB
See original GitHub issueWhen downloading a file/blob smaller than 32MB, the property completeSize in SpeedSummary returned by FileService.getFileToLocalFile() / BlobService.getBlobToLocalFile() won’t get updated, leaving the SpeedSummary useless.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Getting very slow speed while downloading storage blob.
I'll go to download a blob via the storage explorer (in Chrome) and it'll take 2+ minutes to download 35mb. Then even a...
Read more >Download percent come only one time when use Azureblob
• Storage clients have a default limit of 32 MB maximum size for a single block upload . When a block blob upload...
Read more >Upload to Azure Blob Storage with Angular | by Stuart Tottle
Upload multiple files to blob storage and report progress using Angular with a Shared Access Signature (SAS) token generated from your back-end.
Read more >Programmatic file downloads in the browser - LogRocket Blog
Blobs and object URLs exposed. File downloading is a core aspect of surfing the internet. Tons of files get downloaded from the internet ......
Read more >Streaming large blobs through ASP.NET | ticehurst.com
NET origin server instead of through the CDN, the downloads also ... Now update the controller to return a file fetched from Azure...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I was hoping fine-grained updating, because the updating cost is very low.
If the original design is updating per request, the updating when downloading finished is necessary, in case that user may use
SpeedSummary.Even though, I think the updating is not identical in different code paths. For files bigger than 32MB, the updating grain is per 4MB. And for files smaller than 32MB, it’s the whole file size. It’s better to keep it identical.
Please let us know if you have further questions on this.