Re:Alphabet earnings show Google Cloud on $10B run rate
by ssambros on Thursday February 06, 2020 @10:27AM
(#22256658)
To be fair, it seems Memorystore instance is not the same gb-for-gb as Elasticache, since Memorystore gives you extra memory overhead, and on aws you have to manage it yourself. Memorystore also has free network egress/ingress. There is also a RedisLabs offering on Google Cloud with integrated billing.
Disclaimer: I work at Google Cloud.
Re:Alphabet earnings show Google Cloud on $10B run rate
by pdeva1 on Thursday February 06, 2020 @03:01PM
(#22259721)
what do you mean by ‘extra memory overhead’
Re:Alphabet earnings show Google Cloud on $10B run rate
by ssambros on Thursday February 06, 2020 @04:39PM
(#22260638)
if you run Redis you need at least 25% of extra RAM on top the instance memorysize if you want to avoid a lot of nasty OOM scenarios. Memorystore gives this memory by default and in aws you need to tweak the reserved-memory. https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/...
What could be contributing to those large numbers?
[1] - Memorystore only allows vertical scaling, no support for GCP managed Redis clusters, no hybrid functionality (only instances in the same VPC network can access Memorystore, whereas ElastiCache offers all of this.
https://cloud.google.com/memorystore/docs/redis/networking https://cloud.google.com/memorystore/docs/redis/scaling-inst...
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/... https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/...
[2] - https://cloud.google.com/memorystore/ vs. https://aws.amazon.com/elasticache/pricing/