Re:Our service is down because Msft Azure is down. This is h...
by roee on Saturday December 29, 2012 @03:00PM
(#4983227)
When was it? We actually have great experience and great uptime with Azure. It's a very unique case for us.
Re:Our service is down because Msft Azure is down. This is h...
by nodesocket on Saturday December 29, 2012 @03:02PM
(#4983236)
Are you running Linux or Windows? This was June/July.
Re:Our service is down because Msft Azure is down. This is h...
by roee on Saturday December 29, 2012 @03:08PM
(#4983259)
We're running on their table storage from web roles and worker roles (their platform-as-a-service)
Re:Our service is down because Msft Azure is down. This is h...
by hhudolet on Saturday December 29, 2012 @04:11PM
(#4983493)
I have a VM on azure, and no downtime in last 3 months. Also, didn't notice any problems with disks.
Re:Our service is down because Msft Azure is down. This is h...
by jspaur on Saturday December 29, 2012 @05:03PM
(#4983649)
I'd second this. I've found that VM's (especially Windows) run even more reliably than what I had on EC2 (sometimes the machines just got soooo slow on EC2 for no apparent reason)
Re:Our service is down because Msft Azure is down. This is h...
by ismarc on Saturday December 29, 2012 @05:15PM
(#4983691)
When a server gets slow, log in and look at top or vmstat. There's a field called st that stands for steal time. If you're using a micro, you have higher peak CPU available, but lower baseline. We found they were notoriously bad about the average CPU we got and our default is now a small (we also moved to non-ebs backed instances for the primary drive for other reasons, which is unavailable on micros). If your steal time is high, you're over your CPU budget and it's time to look at a bigger instance.
I know its early, and they are just starting, but I just don't have confidence in Azure. Stick with AWS, Linode, Softlayer.