New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please Clarify The Pricing Tier That Non-Production Slots Use For Web Apps On Containers #7399

Closed
rhizohm opened this Issue Apr 18, 2018 — with docs.microsoft.com · 8 comments

Comments

Projects
None yet
3 participants

rhizohm commented Apr 18, 2018 — with docs.microsoft.com

"Scaling is not available for non-production slots."

This statement needs clarification and elucidation. It is not clear from the documentation the "hardware" configuration used by Non-Production slots. This comes into play when load testing on a non-production slot. For example, let's say I am running S1 Standard (1 Core and 1.72 GB RAM). If I deploy a Docker container to a non production slot, is it running on that hardware in isolation or is it "sharing" that hardware with the production slot? If I scale up to an S2, does that only pertain to the production slot or all the slots, or is it shared between them?

Similarly, if I "scale out" with increased instances, does this only apply to the production slot or to all the slots?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@BryanTrach-MSFT

This comment has been minimized.

Show comment
Hide comment
@BryanTrach-MSFT

BryanTrach-MSFT Apr 18, 2018

Member

@rhizohm Thanks for the feedback! We are currently investigating and will update you shortly.

Member

BryanTrach-MSFT commented Apr 18, 2018

@rhizohm Thanks for the feedback! We are currently investigating and will update you shortly.

@BryanTrach-MSFT

This comment has been minimized.

Show comment
Hide comment
@BryanTrach-MSFT

BryanTrach-MSFT Apr 23, 2018

Member

@rhizohm By default, slots share the hardware with the parent site. App Service Plans have the ability to host multiple sites/testing slots. Any scaling (in or out) is applied for any slot or site running within the App Service Plan.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Member

BryanTrach-MSFT commented Apr 23, 2018

@rhizohm By default, slots share the hardware with the parent site. App Service Plans have the ability to host multiple sites/testing slots. Any scaling (in or out) is applied for any slot or site running within the App Service Plan.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@rhizohm

This comment has been minimized.

Show comment
Hide comment
@rhizohm

rhizohm Apr 23, 2018

@BryanTrach-MSFT so if I were to use a slot for load testing, it could tax the experience for users hitting production, is that correct? By the way, this would be in the case of app service for containers. I'm curious about the architecture under the hood here -- I get that in the case of app services, it is IIS under the hood that is serving the different slots from the same hardware. But in the case of app service for containers, I am assuming that the IIS server in front of the app service for container proxies the call to that container, which is isolated.

So, the question is, in the case of app services for containers, does taxing a non-production slot with load affect the production slot?

rhizohm commented Apr 23, 2018

@BryanTrach-MSFT so if I were to use a slot for load testing, it could tax the experience for users hitting production, is that correct? By the way, this would be in the case of app service for containers. I'm curious about the architecture under the hood here -- I get that in the case of app services, it is IIS under the hood that is serving the different slots from the same hardware. But in the case of app service for containers, I am assuming that the IIS server in front of the app service for container proxies the call to that container, which is isolated.

So, the question is, in the case of app services for containers, does taxing a non-production slot with load affect the production slot?

@BryanTrach-MSFT

This comment has been minimized.

Show comment
Hide comment
@BryanTrach-MSFT

BryanTrach-MSFT Apr 23, 2018

Member

@rhizohm Your understanding is correct. Web App for Containers has a shared front end server that distributes the requests to your dedicated web workers (App Service Plan). Any slots for your container are run on the same VM/Web Worker/App Service Plan. In this regard, slots are not ideal for load/performance testing unless you were testing during off hours for your site/container.

Member

BryanTrach-MSFT commented Apr 23, 2018

@rhizohm Your understanding is correct. Web App for Containers has a shared front end server that distributes the requests to your dedicated web workers (App Service Plan). Any slots for your container are run on the same VM/Web Worker/App Service Plan. In this regard, slots are not ideal for load/performance testing unless you were testing during off hours for your site/container.

@rhizohm

This comment has been minimized.

Show comment
Hide comment
@rhizohm

rhizohm Apr 24, 2018

@BryanTrach-MSFT great thanks for clarifying.

What you said below seems to contradict the docs, unless I'm misunderstanding. The docs say "Scaling is not available for non-production slots." but from what you are saying, any slots for my container are run in the same VM/Web Worker/App Service plan. So, if I were to scale up/out, wouldn't all of the containers experience the benefits of that scale?

I guess, can you clarify exactly what is meant by the statement "Scaling is not available for non-production slots."?

rhizohm commented Apr 24, 2018

@BryanTrach-MSFT great thanks for clarifying.

What you said below seems to contradict the docs, unless I'm misunderstanding. The docs say "Scaling is not available for non-production slots." but from what you are saying, any slots for my container are run in the same VM/Web Worker/App Service plan. So, if I were to scale up/out, wouldn't all of the containers experience the benefits of that scale?

I guess, can you clarify exactly what is meant by the statement "Scaling is not available for non-production slots."?

@BryanTrach-MSFT

This comment has been minimized.

Show comment
Hide comment
@BryanTrach-MSFT

BryanTrach-MSFT Apr 24, 2018

Member

@rhizohm I think this document might need some clarity regarding this statement. By saying, "Scaling is not available for non-production slots." it used to be that you could only scale the app service plan on the parent app and both the scale out and scale up blades were grayed out. That was back in 2016 and the platform/scaling has received UI enhancements that allow you to edit the App Service Plan tier in either the parent app or any of the slots. The same rules still apply. By default, your slots run on the same VM/Web worker/App Service Plan as the parent app.

@cephalin There appears to be to items of feedback here regarding the below points in the doc. Can you please review the feedback and update the doc as necessary?

"When your app has multiple slots, you cannot change the tier." - This is not true anymore. I am able to scale up and scale out with two slots on my web apps.
"Scaling is not available for non-production slots." - This statement is confusing and relates to the feedback the customer is proving in this GitHub issue. It might help to make it known that by default, the slot is running on the parent app App Service Plan or something along those lines.

Member

BryanTrach-MSFT commented Apr 24, 2018

@rhizohm I think this document might need some clarity regarding this statement. By saying, "Scaling is not available for non-production slots." it used to be that you could only scale the app service plan on the parent app and both the scale out and scale up blades were grayed out. That was back in 2016 and the platform/scaling has received UI enhancements that allow you to edit the App Service Plan tier in either the parent app or any of the slots. The same rules still apply. By default, your slots run on the same VM/Web worker/App Service Plan as the parent app.

@cephalin There appears to be to items of feedback here regarding the below points in the doc. Can you please review the feedback and update the doc as necessary?

"When your app has multiple slots, you cannot change the tier." - This is not true anymore. I am able to scale up and scale out with two slots on my web apps.
"Scaling is not available for non-production slots." - This statement is confusing and relates to the feedback the customer is proving in this GitHub issue. It might help to make it known that by default, the slot is running on the parent app App Service Plan or something along those lines.

@cephalin

This comment has been minimized.

Show comment
Hide comment
@cephalin

cephalin Apr 25, 2018

Contributor

@dariagrigoriu Can you verify the feedback below?

"When your app has multiple slots, you cannot change the tier." - This is not true anymore. I am able to scale up and scale out with two slots on my web apps.

Contributor

cephalin commented Apr 25, 2018

@dariagrigoriu Can you verify the feedback below?

"When your app has multiple slots, you cannot change the tier." - This is not true anymore. I am able to scale up and scale out with two slots on my web apps.

@cephalin

This comment has been minimized.

Show comment
Hide comment
@cephalin

cephalin May 7, 2018

Contributor

Text updated. #please-close.

Contributor

cephalin commented May 7, 2018

Text updated. #please-close.

@rhizohm rhizohm closed this May 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment