Azure Blob Upload Speed – Don’t use OpenWriteAsync()

Uploading to Azure Storage with the .NET Client can often require some customisation to ensure acceptable performance. First, let’s look at some options in BlobRequestOptions:


The minimum size of a blob before it’ll be uploaded in ‘chunks’. This only works for the non-stream based upload methods.

Minimum: 1MB, or 1,048,576 bytes.


The maximum number of upload operations to perform in parallel, for a single blob.

There’s also a useful property on the Blob itself:


The size of each block to upload. So, for example, if you set to 1MB, a 4MB file will be chunked into 4 separate 1MB blocks.

Default value: 4MB, or 4,194,304 bytes.

// Options
var options = new BlobRequestOptions
    SingleBlobUploadThresholdInBytes = 1024 * 1024, //1MB, the minimum
    ParallelOperationThreadCount = 1

client.DefaultRequestOptions = options;

// Blob stream write
blob.StreamWriteSizeInBytes = 1024 * 1024;

A more thorough explanation is available here:

When it’s all ignored – OpenWriteAsync()

You can set all of these options, but if you use blob.OpenWriteAsync() it’s going to upload files in 5KB chunks as you write to the stream. This will absolutely destroy performance if you’re uploading larger files or a lot of files. Instead, you’ll need to use the blob.UploadFromStreamAsync() method:

// Buffer to a memory stream so that the client uploads in one chunk instead of multiple
// By default the client seems to upload in 5KB chunks
using (var memStream = new MemoryStream())
    // Save to memory stream
    await saveActionAsync(memStream);

    // Upload to Azure
    memStream.Seek(0, SeekOrigin.Begin);
    await blob.UploadFromStreamAsync(memStream);

If you use the UploadFromStreamAsync() method, the settings you set will be honoured and blobs will be uploaded in a much more efficient manner.

Posted by Dan in Azure, C#, 0 comments

Error: Unable to find fileDFUI.exe please verify your install is correct.

I was getting the error ‘Error: Unable to find fileDFUI.exe please verify your install is correct.’ when trying to run an Azure project locally. MS have a rather hefty workaround here which I really didn’t want to use (especially since the error will come back after a while).

An easier workaround is to backup your ServiceConfiguration and ServiceDefinition files and delete the Azure project from your solution, also delete all traces of the Azure project from your solution directory.

Next add an Azure project to your solution (don’t add any roles). Add the roles manually using your existing projects (right-click on ‘Roles’ within the Azure project and select ‘Add > <X> Project in Solution’.

Restore your backed up service config files and you should be good to go!

Posted by Dan in Azure, General, 1 comment