The Windows Azure Accelerator for Umbraco was an open-source tool developed jointly by Microsoft and the Umbraco community around 2011–2012 to help developers quickly package, deploy, and scale Umbraco websites on legacy Windows Azure Cloud Services (specifically Web Roles).
Microsoft officially deprecated the Accelerator following the release of modern Azure Web Sites (now known as Azure App Service). Today, optimizing an Umbraco web app no longer involves this legacy accelerator. Instead, it relies on modern Azure Cloud architecture, native environment settings, and optimized caching. The Legacy Accelerator & Its Core Bottleneck
In the early days of cloud architecture, the Windows Azure Accelerator for Umbraco automated deployment to Azure Web Roles. However, developers quickly encountered severe optimization bottlenecks:
High Storage Transaction Costs: Because Umbraco continuously read and wrote XML configuration files, Lucene search indexes, and media directly to Azure Blob Storage, it generated millions of storage transactions. This severely degraded performance and led to massive, unexpected cloud bills.
The Solution Back Then: Optimizing via the accelerator required developers to rewrite the local storage configuration, routing frequent read/write items to the role instance’s local virtual hard drive (local storage) rather than hitting remote cloud storage for every request. Modern Optimization: Umbraco on Azure App Service
Modern optimization bypasses the old accelerator entirely. If you are hosting an Umbraco web app on Microsoft Azure, use the following modern best practices to “accelerate” and optimize your site: 1. Shift Temporary Files to Local Environment Storage
By default, Azure App Service uses a shared network file system. If Umbraco reads and writes its temporary data here, file locks and extreme slowdowns occur.
Action: Configure Umbraco to generate its cache and temporary files inside the local server environment’s temp folder instead of the shared web application directory. This drastically boosts IOPS performance. 2. Offload Media to Azure Blob Storage
Storing images and video assets on the Web App’s file system slows down backups, scale-out times, and server response times.
Action: Install the Umbraco.StorageProviders.AzureBlob package. This offloads all media assets directly to an Azure Storage Account, utilizing an optimized cache folder for processed media images. 3. Use Redis for Session and Caching Running Umbraco on Azure Web Apps | CMS
Leave a Reply