4 ms·

Why would I want to triple my capacity? Most people don't need to scale to a billion users overnight.

jaywalk 5y ago
Many B2B-type applications have a lot of usage during the workday and minimal usage outside of it. No reason to keep all that capacity running 24/7 when you only need most of it for ~8 hours per weekday. The cloud is perfect for that use case.
- iso1210 5y ago
  Is it really? How much does that scaling actually cost? And what's a workday anyway, surely you operate globally?
  - jaywalk 5y ago
    Scaling itself costs nothing, but saves money because you're not paying for unused capacity. The main application I run operates in 7 countries globally, but the US is the only one that has enough usage to require additional capacity during the workday. So out of 720 hours in a 30 day month, cloud scaling allows me to pay for additional capacity for only the (roughly) 160 hours that it's actually needed. It's a significant cost saver. And because the scaling is based on actual metrics, it won't scale up on a holiday when nobody is using the application. More cost savings.
    - vp8989 5y ago
      You are (conveniently or not) incorrectly assuming that the unit price of provisioned vs on-demand capacity is the same. It's not.
      - jaywalk 5y ago
        Nice of you to assume that I don't understand the pricing of the services I use. I can assure you that I do, and I can also assure you that there is no such thing as provisioned vs on-demand pricing for Azure App Service until you get into the higher tiers. And even in those higher tiers, it's cheaper for me to use on-demand capacity. Obviously what I'm saying will not apply to all use cases, but I'm only talking about mine.
- deleted 5y ago
  [deleted]
- dijit 5y ago
  idk man, idle hardware doesn't use all that much power. https://www.thomas-krenn.com/en/wiki/Processor_P-states_and_C-states https://www.thomas-krenn.com/en/wiki/Processor_P-states_and_... Which is an implementation of: https://web.eecs.umich.edu/~twenisch/papers/asplos09.pdf https://web.eecs.umich.edu/~twenisch/papers/asplos09.pdf

Many B2B-type applications have a lot of usage during the workday and minimal usage outside of it. No reason to keep all that capacity running 24/7 when you only need most of it for ~8 hours per weekday. The cloud is perfect for that use case.

iso1210 5y ago
Is it really? How much does that scaling actually cost? And what's a workday anyway, surely you operate globally?
- jaywalk 5y ago
  Scaling itself costs nothing, but saves money because you're not paying for unused capacity. The main application I run operates in 7 countries globally, but the US is the only one that has enough usage to require additional capacity during the workday. So out of 720 hours in a 30 day month, cloud scaling allows me to pay for additional capacity for only the (roughly) 160 hours that it's actually needed. It's a significant cost saver. And because the scaling is based on actual metrics, it won't scale up on a holiday when nobody is using the application. More cost savings.
  - vp8989 5y ago
    You are (conveniently or not) incorrectly assuming that the unit price of provisioned vs on-demand capacity is the same. It's not.
    - jaywalk 5y ago
      Nice of you to assume that I don't understand the pricing of the services I use. I can assure you that I do, and I can also assure you that there is no such thing as provisioned vs on-demand pricing for Azure App Service until you get into the higher tiers. And even in those higher tiers, it's cheaper for me to use on-demand capacity. Obviously what I'm saying will not apply to all use cases, but I'm only talking about mine.
deleted 5y ago
[deleted]
dijit 5y ago
idk man, idle hardware doesn't use all that much power. https://www.thomas-krenn.com/en/wiki/Processor_P-states_and_C-states https://www.thomas-krenn.com/en/wiki/Processor_P-states_and_... Which is an implementation of: https://web.eecs.umich.edu/~twenisch/papers/asplos09.pdf https://web.eecs.umich.edu/~twenisch/papers/asplos09.pdf