Windows Azure Worker Role Showing High CPU

I was recently troubleshooting an issue where a Worker Role was deployed on Windows Azure.The Role had 3 instances and during most of the time all the instances used to run at 99% + CPU. The instances query a database, gets social media posts and send emails. Most of the time all the  instances would peg at 99% CPU…


Service Bus Brokered Messaging: Unexpected Error Sending Messages Larger than 256K

When sending a message to a Azure Service Bus Brokered message queue or topic, with the .Net client library (Microsoft.ServiceBus.dll) and, the size of the message exceeds 256KB (current max message size documented under Windows Azure Service Bus Quotas), you will see the below error. The same error reoccurs when attempting to resend the message….


Enable Server GC mode for your worker role

If you are using an Azure worker role that is memory intensive you may notice that the performance of your application is not optimal.One of the symptoms is a high CPU utilization combined with a high value for the “% Time in GC” performance counter. Typical workloads are WCF applications that handle many client requests. You might be able…

Windows Azure Cache: Feature Comparison Matrix

Windows Azure offers three different Cache Offerings. 1. Cache Service Preview 2. In-Role Caching 3. Shared Caching Cache Service is the newest and is in Preview right now. Considering that Shared Caching is soon to be deprecated (ref), the real choice is between the new Cache Service Preview and the tried and tested In-Role Caching….


Multiple Domain Name to the same Cloud Service and SSL Certificates

So most probably you got the following error while browsing a cloud service hosted in Windows Azure. There is a problem with this website’s security certificate. The security certificate presented by this website was not issued by a trusted certificate authority. Security certificate problems may indicate an attempt to fool you or intercept data…


One Thing You Must Do When: Service Endpoint is showing Offline in Azure Traffic Manager

Recently I came across multiple scenarios where the Service endpoints were showing Offline/Degraded in Traffic Manager. Those endpoints were valid, accessible and respective service was running fine, but still the end point was showing offline in Traffic Manager. In the above screenshot, the respective endpoint is accessible fine, but the Traffic Manager is showing it…