5 ms·

Sorry for the lack of clarity (I've tilted at this windmill, and failed). E2-std-2 != t3.large. A t3.large only has a "baseline performance" of 30% [1]. That's

by boulos 7y ago

Sorry for the lack of clarity (I've tilted at this windmill, and failed). E2-std-2 != t3.large. A t3.large only has a "baseline performance" of 30% [1]. That's more like our e2-small though they have more memory. Instead, I'd compare e2-std-2 to m5.large like you started to do so. An m5.large on-demand is $.096/hr => $70/month, while the e2-std-2 is $48/month. I think your $41.75/month is from the 1-yr Standard RI (a 40% discount). For that, the most direct comparison would be to use a Committed Use Discount on our side which comes with a similar percentage discount (I can't find this on my phone right now) so that's like $29/month. Does that make sense? [1] https://aws.amazon.com/ec2/instance-types/t3/ https://aws.amazon.com/ec2/instance-types/t3/

mythz 7y ago
As stated I'm only trying to get a comparison of the cost for the very popular use-case of running a "Website 24/7 for 12 months". I use this simple basic core metric as a baseline for comparing hosting costs amongst different hosting providers. This is trivial to work out in AWS, I just go to their Reversed Pricing Page [2], look for the total cost for an m5.large (2x VCPU/8GB RAM) instance for 12 months which is $501 (12 x 41.75). I'd like to be able to do the same for GCP, I see the committed usage page [2] but I don't see any easy way to work out the cost for 12 months / 24/7, it mentions things like "discount is up to 57% for most resources like machine types or GPUs", what does "up to" mean? Is that the discount for running 24/7? So is the E2-Std-2 monthly price of a $48.92 * (1 - .57) = $21.04? All I see back in GCP's compute pricing page related to "committed usage" is "1 year commitment price" of "$10.03 / vCPU month" but this says it's for "E2 custom vCPUs and memory", does this apply to E2-Std-2 instances? So is the cost for 2x VCPU = $10.03 x 2 + 8GB = 8x $1.34 = 10.72 for the total monthly cost of $30.78? If it's not how am I supposed to workout what E2-Std-2 cost of 12 months / 24/7 is? It's frustrating that there's no clear/easy way to determine the pricing of a simple and popular hosting scenario like this. [1] https://aws.amazon.com/ec2/pricing/reserved-instances/pricing/ https://aws.amazon.com/ec2/pricing/reserved-instances/pricin... [2] https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts https://cloud.google.com/compute/docs/instances/signing-up-c...
- boulos 7y ago
  I agree that our tables are inconsistent for E2 (I sent an email about this internally, we'll try to get it fixed). tl;dr: You did calculate it right. $10.3/vCPU/month x 2 vCPU + $1.34/GB/month x 8 GB for a 1-year commitment aka $30.78/month (and $22/month for a 3-year commitment). All of the predefined shapes are just "how many vCPUs times $/vCPU + how many GBs times $/GB". Ignoring the lack of columns for commitment pricing in the predefined shapes tables (which some instance types have and some don't... grr), I want to explain the reasoning. One thing that's different for GCP vs AWS is that we actually don't have a SKU for e2-standard-2 or e2-standard-16. We instead do "Resource Based Pricing" [1], and there's only "E2 Instance Core" and "E2 Instance Ram" or whatever. So if you have 100 e2-standard-2s and 100 e2-standard-16s running for a month, your bill will have two line items: - 1800 vCPUs times 2.6M seconds of Predefined E2 vCPU - 7200 GB times 2.6M seconds of Predefined E2 GB Memory The price for E2 is apparently the same ($10.03/vCPU/month) for both Custom vCPUs as well as Predefined vCPUs [2] (meaning the price for your vCPUs is the same whether you make a custom E2 with 8 vCPUs and 29 GB of memory, or use an e2-standard-8 which has the same 8 vCPUs and 32 GB). Memory is the same (your $1.34/GB/month for a 1-year commitment). Hope that makes sense. We'll try to improve the docs. Sorry. [1] https://cloud.google.com/blog/products/gcp/announcing-resource-based-pricing-for-google-compute-engine https://cloud.google.com/blog/products/gcp/announcing-resour... [2] https://cloud.google.com/compute/all-pricing#e2_machine-types https://cloud.google.com/compute/all-pricing#e2_machine-type...
  - cobookman 7y ago
    However n1 and other instance classes have different sku pricing for custom vs predefined pricing. E.g. n1 predefined machine bills $0.031611 / vCPU hour. Whereas a custom sized n1 machine is $0.033174 / vCPU hour
- nl 7y ago
  You can just go to their calculator (which I find much better than the AWS one). Here it is with the 1 year committed use: https://cloud.google.com/products/calculator/#id=79186cdb-1828-410c-93f2-271386db67dd https://cloud.google.com/products/calculator/#id=79186cdb-18... ($30.82/month) 3 year committed use: https://cloud.google.com/products/calculator/#id=afd446fc-7485-4518-8b6b-ae363b204da3 https://cloud.google.com/products/calculator/#id=afd446fc-74... ($22.01/month) And here without: https://cloud.google.com/products/calculator/#id=3ff5d861-7557-4d20-885c-03610d3eb0f0 https://cloud.google.com/products/calculator/#id=3ff5d861-75... ($48.92/month)
ti_ranger 7y ago
> A t3.large only has a "baseline performance" of 30% > Instead, I'd compare e2-std-2 to m5.large like you started to do so. Yes, a "baseline performance" of 100% would more or less be an M-family instance, but with additional overhead to manage noisy neighbors etc. (and thus T-family is slightly more expensive for the same constant performance than M-family). T-family is specifically for non-constant workloads where CPU over-commit provides value, but without memory over-commit, which can result in highly-variable performance. Neither T-family or M-family do "memory stealing" aka memory overcommit, like GCP's E2 seemingly does (but the pricing page doesn't explicitly state this, and your detailed comparisons omit this crucial difference). So, apples and oranges; you shouldn't really "compare" without benchmarking ... What is the "baseline" memory GCP E2 instances get?

by boulos 7y ago

mythz 7y ago

As stated I'm only trying to get a comparison of the cost for the very popular use-case of running a "Website 24/7 for 12 months". I use this simple basic core metric as a baseline for comparing hosting costs amongst different hosting providers. This is trivial to work out in AWS, I just go to their Reversed Pricing Page [2], look for the total cost for an m5.large (2x VCPU/8GB RAM) instance for 12 months which is $501 (12 x 41.75). I'd like to be able to do the same for GCP, I see the committed usage page [2] but I don't see any easy way to work out the cost for 12 months / 24/7, it mentions things like "discount is up to 57% for most resources like machine types or GPUs", what does "up to" mean? Is that the discount for running 24/7? So is the E2-Std-2 monthly price of a $48.92 * (1 - .57) = $21.04? All I see back in GCP's compute pricing page related to "committed usage" is "1 year commitment price" of "$10.03 / vCPU month" but this says it's for "E2 custom vCPUs and memory", does this apply to E2-Std-2 instances? So is the cost for 2x VCPU = $10.03 x 2 + 8GB = 8x $1.34 = 10.72 for the total monthly cost of $30.78? If it's not how am I supposed to workout what E2-Std-2 cost of 12 months / 24/7 is? It's frustrating that there's no clear/easy way to determine the pricing of a simple and popular hosting scenario like this. [1] https://aws.amazon.com/ec2/pricing/reserved-instances/pricing/ https://aws.amazon.com/ec2/pricing/reserved-instances/pricin... [2] https://cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts https://cloud.google.com/compute/docs/instances/signing-up-c...

boulos 7y ago
I agree that our tables are inconsistent for E2 (I sent an email about this internally, we'll try to get it fixed). tl;dr: You did calculate it right. $10.3/vCPU/month x 2 vCPU + $1.34/GB/month x 8 GB for a 1-year commitment aka $30.78/month (and $22/month for a 3-year commitment). All of the predefined shapes are just "how many vCPUs times $/vCPU + how many GBs times $/GB". Ignoring the lack of columns for commitment pricing in the predefined shapes tables (which some instance types have and some don't... grr), I want to explain the reasoning. One thing that's different for GCP vs AWS is that we actually don't have a SKU for e2-standard-2 or e2-standard-16. We instead do "Resource Based Pricing" [1], and there's only "E2 Instance Core" and "E2 Instance Ram" or whatever. So if you have 100 e2-standard-2s and 100 e2-standard-16s running for a month, your bill will have two line items: - 1800 vCPUs times 2.6M seconds of Predefined E2 vCPU - 7200 GB times 2.6M seconds of Predefined E2 GB Memory The price for E2 is apparently the same ($10.03/vCPU/month) for both Custom vCPUs as well as Predefined vCPUs [2] (meaning the price for your vCPUs is the same whether you make a custom E2 with 8 vCPUs and 29 GB of memory, or use an e2-standard-8 which has the same 8 vCPUs and 32 GB). Memory is the same (your $1.34/GB/month for a 1-year commitment). Hope that makes sense. We'll try to improve the docs. Sorry. [1] https://cloud.google.com/blog/products/gcp/announcing-resource-based-pricing-for-google-compute-engine https://cloud.google.com/blog/products/gcp/announcing-resour... [2] https://cloud.google.com/compute/all-pricing#e2_machine-types https://cloud.google.com/compute/all-pricing#e2_machine-type...
- cobookman 7y ago
  However n1 and other instance classes have different sku pricing for custom vs predefined pricing. E.g. n1 predefined machine bills $0.031611 / vCPU hour. Whereas a custom sized n1 machine is $0.033174 / vCPU hour
nl 7y ago
You can just go to their calculator (which I find much better than the AWS one). Here it is with the 1 year committed use: https://cloud.google.com/products/calculator/#id=79186cdb-1828-410c-93f2-271386db67dd https://cloud.google.com/products/calculator/#id=79186cdb-18... ($30.82/month) 3 year committed use: https://cloud.google.com/products/calculator/#id=afd446fc-7485-4518-8b6b-ae363b204da3 https://cloud.google.com/products/calculator/#id=afd446fc-74... ($22.01/month) And here without: https://cloud.google.com/products/calculator/#id=3ff5d861-7557-4d20-885c-03610d3eb0f0 https://cloud.google.com/products/calculator/#id=3ff5d861-75... ($48.92/month)

ti_ranger 7y ago

> A t3.large only has a "baseline performance" of 30% > Instead, I'd compare e2-std-2 to m5.large like you started to do so. Yes, a "baseline performance" of 100% would more or less be an M-family instance, but with additional overhead to manage noisy neighbors etc. (and thus T-family is slightly more expensive for the same constant performance than M-family). T-family is specifically for non-constant workloads where CPU over-commit provides value, but without memory over-commit, which can result in highly-variable performance. Neither T-family or M-family do "memory stealing" aka memory overcommit, like GCP's E2 seemingly does (but the pricing page doesn't explicitly state this, and your detailed comparisons omit this crucial difference). So, apples and oranges; you shouldn't really "compare" without benchmarking ... What is the "baseline" memory GCP E2 instances get?