Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
How long does it take to spin up a new instance of a website on the azure platform?
So If I have 1 instance and I want to increase to say 3 - how long will it take for the other 2 instances to serve requests?
Thanks
With Azure Websites it is instant (few seconds) - under assumption there is incoming traffic to activate those instances. Azure Websites has already a pool of machines standing by, so the only thing you notice is a cold start of your site on a new machine.
I just did this. It took just under 10 minutes. Although not instant, this seems reasonable for most scenarios, especially if you know that your site is about to be hit. What is important though, is that this answer is really only a guess. There are many variables that could affect this massively:
I was using a smallish .Net web service - a larger app could be slower to deploy?
My service runs on Windows Server 2012 - are other editions faster/slower?
Do MS sometimes have new VMs on standby for quick deployment?
I'm sure the Azure centres are busier/slower at certain times than others
If you have a large/slow set of startup scripts, this will all add time
I don't know answers to any of those but hopefully this gives you an idea.
EDIT: Just to be clear - I did this on Cloud Services, not "Web Sites", which I don't have any of! I'm not always sure whether OPs know the difference - I used to call my Web Sites for ages!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
We are looking for a cloud based solution for messaging queue. We have chosen RabbitMQ and we already have few app that are using this. RabbitMQ is hosted locally. For testing purposes it was ok, but right now when business is growing and we are looking into centralised RabbitMQ with HA we are looking into cloud solution.
My question is: which service would you recommend for RabbitMQ,
the options that we've found are:
cloudamqp.com/
https://addons.heroku.com/rabbitmq-bigwig
https://bitnami.com and use Azure
or
host it in Azure and manage by ourself - but we would like to avoid this as much as possible - not enough human resources to look after that.
What would you recommend?
my suggestion is http://cloudamqp.com - i use them for just about of all my RabbitMQ hosting needs, for production web apps.
it's a fully managed RabbitMQ hosting service. you don't have to worry about much, and you can get as large / scalable as you need. From very small and cheap, to enterprise level hosting with clustering, etc.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
We've recently set-up our resources in our Azure Portal and especially giving rights was a lot of work.
I wonder if we did it correctly and in the proper order. Our web application seems to work fine.
Next week our client wants us to set-up our environment in his account. This time I want to do it properly ;)
What is the best approach to do this? I don't want to bother him everytime I need to change something.
The situation:
2 developers. 1 of them (myself) needs to add extra resources.
1 resource group
Web app using the S1 plan
4 deployment slots. 2 will be created right away, the other two later
1 Storage account
1 SQL Server
1 Elastic pool
Several SQL databases. Some will be created by code.
The last time I needed to give my co-worker access to each resources in the project. I assume that can be done eassier.
What role do I need myself to be able to access all resources and create deployment slots, create databases and set-up continuous build?
Assuming that all the relevant resources are located in the same resource group (which is the recommended pattern), you just need to give Contributor access to the resource group, and it will apply to everything in it.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
OK,
I am setting up my first Azure VM, the only images available are basically windows server.
Why are their servers so low on memory until you get to pretty big $$$?
Are there any of us who would straight faced tell a client that they should run a windows server with .75 GB of ram?
Can I run basic applications on the small machines or should I not waste my time?
Thank you,
Joe
not sure where you're looking at, but there's definitely more than Windows images in there (Ubunto, CoreOs, CentOS, Suse...)
Not to mention that you also have the VM Depot
extra small instances make good for some light load like acting as a witness in HA setups, or even running small web sites...
depends on what you run on it.
you'd know better what your app requires.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I found some technical articles which mentioned that i need to have three separate servers for SharePoint production environment;
- First one is for the Database,
- Second server for Application,
- and the third for the front-end.
But in my case i am planning to have only two servers one for the Database and the other for the application and front-end, will it still be valid to have two servers .Baring in mind that me deployment is considered somehow small with around 60 internal users and around 100 external users?
You can set it up this way. The difference will be in how many SharePoint Service Applications you start on each box.
In environments that have three machines you will see that the there is one box dedicated to the web front end and another that runs the desired SharePoint Applications such as Search, Excel Services, PerformancePoint etc. Since those applications are memory and processor intensive it is best to keep them on a separate machine.
Your performance may vary based on the scale of hardware in your box and how many of those Services Applications you need to kick off.
Some Service Applications can cause a lot of load and need to be finely tuned such as Excel Services and PerformancePoint. I recommend you looking into each that you plan on starting to determine if you will put too much load on your machine
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am just thinking of moving a website from a VPS to Windows Azure Web Sites. After doing a load test, I accidentally took down my test website, using around 30MB over the daily bandwidth.
This made me wonder what would happen if my website was suddenly hit by a DDOS attack? I'm pretty sure everything would max out the daily and hourly limits in no time, even worse, redirecting all the users to the azure over limit notification.
Is there anything that can be done about that? I know the daily bandwidth limit will be harder to reach after I put all the images on a CDN, but I'm afraid what would happen if there's a spike or something.
Sorry for such an answer with no head and tail. I hope you guys will understand.
Windows Azure has built-in load balancers that will stave off most (if not all) DOS type attacks. The truth is, Microsoft is very hush-hush on the specifics of how their load balancers protect against malicious attacks (as they should be).
An added benefit to hosting your applications in the cloud is that you can take advantage of auto-scaling when you get heavy loads (malicious or otherwise) so your site won't go down.
You might want to check out the Security Best Practices For Developing Windows Azure Applications document for more information on this.