26
votes

We have sold our first 2 small Azure real world implementations and have set them all up and are now getting hit with extremely bad feedback from the clients over performance.

One of them is setup as the following:

  Domain Controller – A2
  Terminal Server – A3

The terminal server is on an A3 plan (as it’s only a micro client of 2-4 concurrent users) and is horrendously slow. It takes 10-15 seconds to load websites in Internet Explorer (even during testing today it took 10 seconds to load sites such as Telstra's site or Sydney Morning Heralds site).

It also takes on average 8 seconds to load Microsoft Excel (without even loading a file). This is a vanilla install of Excel 2013 on Server 2012 R2 with the RDS role. We initially advised the client they should be fine on an A2 plan, however after they first complained about speeds, we moved them to A3 which made next to no discernible difference (and task manager is showing the machine not even coming close to using any resources).

Performance testing is showing that the disk subsystems are slower than our desktop SATA machines – which could be related (which a quick Google search of “Azure slow disk io” shows that we aren’t alone here).

Our team here have run up an Amazon instance (with smaller specs than the A3 plan) and it is lightning fast doing the exact same things. We have also benchmarked on another Virtual Machine host that we used to use as we still have clients there from before we decided to start selling Azure and they are also lightning fast doing the same things.

In this particular case, the speeds they are getting are much, much slower than the 5 year old server that was replaced, which doesn’t bode too well for us unfortunately.

Another one of our clients other clients has exactly the same slow performance on their RDS server, especially around browsing the Internet. Speed tests on both show huge amount of speed (i.e. 500Mbit +) but daily usage doesn’t reflect that at all. It honestly feels like the Internet is operating at dial up speeds.

We've purchased a developer support pack and tried to lodge support instances, however it keeps crashing at the end of creating the request saying "Cannot log a support request at this time. Please contact Microsoft via phone and lodge an Azure request". We try calling via phone and they say they can't lodge them and we have to do it online.

We're desperate here for some help. Can anyone point us in the right direction?

Our guys have spent about 20 hours on this issue and everything points back to the Azure VM's just being super slow compared to other cloud providers (Amazon etc).

4
This belongs on ServerFault, not StackOverflow (it's about infrastructure, not programming). - David Makogon
Apologies, first time poster and was directed here from the Azure web page. - Nigel Moore
If the IOPS are the limiting factor, have you considered adding multiple data disks to your vm and striping them into a single volume? I believe you will be charged only for the actual data used, regardless of the disk size, at this tier of storage, so there's no real reason not to put the maximum number of allowed disks into your vm. - Greg D
I'm not sure it's IOPS causing the problem, although it definitely could be. Even with just 1 user logged into the server, opening things like Excel (even without opening a file), Outlook and browsing the Internet is very slow. It seems to be slower at some times than others as well. With this server doing absolutely nothing (no scheduled tasks etc) it really feels like the underlying infrastructure causing the problem. - Nigel Moore
Try logging the support ticket using Internet Explorer - Ben Adams

4 Answers

13
votes

Azure disks are terribly slow. There is a service option called "Premium storage" which should increase the IOPS drastically. Waiting that, I would create a separate volume on top of storage spaces (using as many disks as the VM size allows) in order to get max iops. (8 disks = 8x500 IOPS). Moving the user profiles to that disk should help.

10
votes

I have seen both AWS and AZURE and AZURE is dead slow on drive performance while AWS is fairly snappy. In my opinion, Azure is a terribly inferior product to AWS and that is simply the cause of many problems you would not have on AWS.

5
votes

I set up a SharePoint development environment using my free MSDN Ultimate subscription.

I went with a D12 machine type (see Virtual Machine sizes). It should offer decent IOPS. At least with the D-series there is the promise of "local" SSDs. MSDN documentation contains some numbers on that: MSDN documentation.

Installing StyleCop took hours. Installing Resharper did not even complete.. some Visual Studio component which needs to be called during the setup "did not return in a timely fashion"... I'm not talking seconds here. I'm talking about several tens of minutes of waiting!

Opening the "add/remove programs" window never completes...

I spent 2 hours trying to installed two tiny pieces of software while nothing else was running on the machine. Seriously... that's nowhere even remotely near "productive".

The virtual machine has been deallocated for a few months. I started it up yesterday and shut it down at the end of my investigations (doing some software development). Today I wanted to continue where I left of. Unfortunately the performance degraded since yesterday. I was hoping it would actually perform better due to more frequent use (second day in a row).

That's a really sad picture. Fortunately my subscription is "free"...

5
votes

i ran a comparison on an Azure VM versus my own personal development workstation.

enter image description here

The image above shows the specs between my personal developer workstation and our VM server in Azure.

Both machines are running 16 Gig of Ram, 64 bit windows and both running SSD drives. My i7 processor is 3 ghz versus the 2.2 ghz processor on the azure box.

My development workstation can restore a sql database backup in 1 minute 30 seconds. In azure it takes 22 minutes and 4 seconds to restore the exact same backup file.

I have contacted microsoft about this to see if they can offer any insight. My local dev workstation is just running on a single C:\ ssd drive with no striping etc.

The above test was conducted on the a2 v2 vm sized hardware and the a2m v2 sized vm hardware. In both instances the database restored in 22 minutes.

enter image description here

enter image description here

Restoring on the d4s v3 line of hardware dropped the restore time drastically to 9 minutes.

enter image description here

So far none of these VMS come anywhere close to the speed of my personal development workstation running sql server on a single ssd drive with basic windows 10 pro.