high_scalability high_scalability-2013 high_scalability-2013-1543 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Authored by Chris Fregly : Former Netflix Streaming Platform Engineer, AWS Certified Solution Architect and Purveyor of fluxcapacitor.com. Ahead of the upcoming 2nd annual re:Invent conference, inspired by Simone Brunozzi’s recent presentation at an AWS Meetup in San Francisco, and collected from a few of my recent Fluxcapacitor.com consulting engagements, I’ve compiled a list of 10 useful time and clock-tick saving tips about AWS. 1) Query AWS resource metadata Can’t remember the EBS-Optimized IO throughput of your c1.xlarge cluster? How about the size limit of an S3 object on a single PUT? awsnow.info is the answer to all of your AWS-resource metadata questions. Interested in integrating awsnow.info with your application? You’re in luck. There’s now a REST API , as well! Note: These are default soft limits and will vary by account. 2) Tame your S3 buckets Delete an entire S3 bucket with a single CLI command:
sentIndex sentText sentNum sentScore
1 Per the AWS documentation, EBS volumes can expect an annual failure rate (AFR) of between 0. [sent-19, score-0.123]
2 Initially, provision your instance to the minimum size possible. [sent-25, score-0.156]
3 6) Avoid noisy neighbors In any multi-tenant, non-dedicated, virtualized environment like AWS, you will certainly experience the noisy neighbor effect measured by CPU Steal. [sent-29, score-0.808]
4 CPU Steal is the percentage of time that your virtualized guest is involuntarily waiting for physical host CPU from another guest. [sent-30, score-0.293]
5 When using EBS-backed EC2 instances, you can flee a noisy environment by simply stopping and starting the instance. [sent-32, score-0.268]
6 Of course, you’ll need to make sure your healthcheck policies don’t terminate the instance before it restarts. [sent-33, score-0.176]
7 You can avoiding noisy neighbors by preferring larger EC2 instance types. [sent-35, score-0.518]
8 Larger virtualized guest instances require more physical host resources - and therefore the host can support less overall tenants. [sent-36, score-0.483]
9 micro’s are extremely noisy and bursty - similar to my old college-dorm neighbors above. [sent-39, score-0.422]
10 The most effective way to avoid noisy neighbors, however, is to pay extra for dedicated EC2 instances. [sent-40, score-0.382]
11 8) Avoid underperforming CPU architectures for your workload Different CPU architectures enable better performance for certain workloads depending on the NUMA characteristics, cache sizes, number of cores, number of hardware threads, GPU, etc. [sent-53, score-0.118]
12 If you’re sensitive to cost, you can run the instance for 55 minutes, then terminate it. [sent-59, score-0.176]
13 Another benefit is that VPC enable ELB’s as a middletier load balancer behind a private subnet. [sent-65, score-0.133]
14 It’s worth noting that Network Address Translation ( NAT ) instances in a VPC are actually EC2 instances performing Port Address Translation (PAT) versus dedicated hardware devices with single-purpose ASIC chips. [sent-68, score-0.53]
15 10) Pre-warm and autoscale-out your AWS resources before expected spikes ELBs - along with other AWS blackbox resources such as NAT, S3, DynamoDB, Glacier, and Beanstalk - are made up of EC2 instances just like your custom application. [sent-69, score-0.186]
16 These instances need to autoscale up and down just like your application - unless you provision them ahead of time. [sent-70, score-0.335]
17 By default, Amazon will do their best to autoscale based on traffic, but it’s always best to notify them for pre-warm and provisioning ahead of an expected spike. [sent-72, score-0.148]
18 252 Notice the 8 ELB instances that are returned. [sent-158, score-0.186]
19 Next, here is dig against a low-traffic, default ELB for my FluxCapacitor open source project demo: $dig edge. [sent-160, score-0.184]
20 Again, these are the instances that makeup the actual ELB - not the instances behind the ELB. [sent-187, score-0.372]
wordName wordTfidf (topN-words)
[('vpc', 0.304), ('aws', 0.296), ('elb', 0.287), ('cloudformation', 0.277), ('noisy', 0.268), ('instances', 0.186), ('neighbors', 0.154), ('virtualized', 0.118), ('afr', 0.118), ('isdigagainst', 0.118), ('ingress', 0.107), ('templates', 0.105), ('default', 0.104), ('noting', 0.1), ('cpu', 0.098), ('instance', 0.096), ('autoscale', 0.089), ('stripe', 0.085), ('netflix', 0.083), ('steal', 0.083), ('nat', 0.08), ('dig', 0.08), ('terminate', 0.08), ('ebs', 0.079), ('translation', 0.073), ('private', 0.068), ('physical', 0.065), ('enable', 0.065), ('annual', 0.065), ('template', 0.061), ('provision', 0.06), ('tips', 0.06), ('provisioning', 0.059), ('volumes', 0.058), ('dedicated', 0.058), ('rds', 0.058), ('host', 0.057), ('avoid', 0.056), ('answer', 0.055), ('metadata', 0.055), ('security', 0.055), ('notice', 0.054), ('brunozzi', 0.053), ('newunified', 0.053), ('violates', 0.053), ('underperforming', 0.053), ('albeit', 0.053), ('involuntarily', 0.053), ('colleague', 0.053), ('cockroft', 0.053)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999976 1543 high scalability-2013-11-05-10 Things You Should Know About AWS
Introduction: Authored by Chris Fregly : Former Netflix Streaming Platform Engineer, AWS Certified Solution Architect and Purveyor of fluxcapacitor.com. Ahead of the upcoming 2nd annual re:Invent conference, inspired by Simone Brunozzi’s recent presentation at an AWS Meetup in San Francisco, and collected from a few of my recent Fluxcapacitor.com consulting engagements, I’ve compiled a list of 10 useful time and clock-tick saving tips about AWS. 1) Query AWS resource metadata Can’t remember the EBS-Optimized IO throughput of your c1.xlarge cluster? How about the size limit of an S3 object on a single PUT? awsnow.info is the answer to all of your AWS-resource metadata questions. Interested in integrating awsnow.info with your application? You’re in luck. There’s now a REST API , as well! Note: These are default soft limits and will vary by account. 2) Tame your S3 buckets Delete an entire S3 bucket with a single CLI command:
2 0.25137451 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
Introduction: This is a guest post by Shawn Hsiao , Luke Massa , and Victor Luu . Shawn runs TripAdvisor ’s Technical Operations team, Luke and Victor interned on his team this past summer. This post is introduced by Andy Gelfond , TripAdvisor’s head of engineering. It's been a little over a year since our last post about the TripAdvisor architecture . It has been an exciting year. Our business and team continues to grow, we are now an independent public company, and we have continued to keep/scale our development process and culture as we have grown - we still run dozens of independent teams, and each team continues to work across the entire stack. All that has changed are the numbers: 56M visitors per month 350M+ pages requests a day 120TB+ of warehouse data running on a large Hadoop cluster, and quickly growing We also had a very successful college intern program that brought on over 60 interns this past summer, all who were quickly on boarded and doing the same kind of work a
3 0.20385288 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure
Introduction: This is a guest post by Frédéric Faure (architect at Ysance ) on the differences between using a cloud infrastructure and building your own. Frédéric was kind enough to translate the original French version of this article into English. I’ve been noticing many questions about the differences inherent in choosing between a Cloud infrastructure such as AWS (Amazon Web Services) and a traditional physical infrastructure. Firstly, there are a certain number of preconceived notions on this subject that I will attempt to decode for you. Then, it must be understood that each infrastructure has its advantages and disadvantages: a Cloud-type infrastructure does not necessarily fulfill your requirements in every case, however, it can satisfy some of them by optimizing or facilitating the features offered by a traditional physical infrastructure. I will therefore demonstrate the differences between the two that I have noticed, in order to help you make up your own mind. The Fram
4 0.19199409 1631 high scalability-2014-04-14-How do you even do anything without using EBS?
Introduction: In a recent thread on Hacker News discussing recent AWS price changes , seldo mentioned they use AWS for business, they just never use EBS on AWS. A good question was asked: How do you even do anything without using EBS? Amazon certainly makes using EBS the easiest path. And EBS has a better reliability record as of late, but it's still often recommended to not use EBS. This avoids a single point of failure at the cost of a lot of complexity, though as AWS uses EBS internally, not using EBS may not save you if you use other AWS services like RDS or ELB. If you don't want to use EBS, it's hard to know where to even start. A dilemma to which Kevin Nuckolls gives a great answer : Well, you break your services out onto stateless and stateful machines. After that, you make sure that each of your stateful services is resilient to individual node failure. I prefer to believe that if you can't roll your entire infrastructure over to new nodes monthly then you're unprepared fo
5 0.16705541 881 high scalability-2010-08-16-Scaling an AWS infrastructure - Tools and Patterns
Introduction: This is a guest post by Frédéric Faure (architect at Ysance ), you can follow him on twitter . How do you scale an AWS (Amazon Web Services) infrastructure? This article will give you a detailed reply in two parts: the tools you can use to make the most of Amazon’s dynamic approach, and the architectural model you should adopt for a scalable infrastructure. I base my report on my experience gained in several AWS production projects in casual gaming (Facebook), e-commerce infrastructures and within the mainstream GIS (Geographic Information System). It’s true that my experience in gaming ( IsCool, The Game ) is currently the most representative in terms of scalability, due to the number of users (over 800 thousand DAU – daily active users – at peak usage and over 20 million page views every day), however my experiences in e-commerce and GIS (currently underway) provide a different view of scalability, taking into account the various problems of availability and da
6 0.16496028 1557 high scalability-2013-12-02-Evolution of Bazaarvoice’s Architecture to 500M Unique Users Per Month
7 0.15300563 1058 high scalability-2011-06-13-Automation on AWS with Ruby and Puppet
8 0.14091066 1353 high scalability-2012-11-01-Cost Analysis: TripAdvisor and Pinterest costs on the AWS cloud
10 0.13341297 1286 high scalability-2012-07-18-Strategy: Kill Off Multi-tenant Instances with High CPU Stolen Time
11 0.1310861 812 high scalability-2010-04-19-Strategy: Order Two Mediums Instead of Two Smalls and the EC2 Buffet
13 0.12643316 1029 high scalability-2011-04-25-The Big List of Articles on the Amazon Outage
14 0.12085619 1278 high scalability-2012-07-06-Stuff The Internet Says On Scalability For July 6, 2012
15 0.11617 1564 high scalability-2013-12-13-Stuff The Internet Says On Scalability For December 13th, 2013
16 0.11449985 1248 high scalability-2012-05-21-Pinterest Architecture Update - 18 Million Visitors, 10x Growth,12 Employees, 410 TB of Data
17 0.11350235 1576 high scalability-2014-01-10-Stuff The Internet Says On Scalability For January 10th, 2014
18 0.11315637 688 high scalability-2009-08-26-Hot Links for 2009-8-26
19 0.11277495 1291 high scalability-2012-07-25-Vertical Scaling Ascendant - How are SSDs Changing Architectures?
20 0.11079811 1112 high scalability-2011-09-07-What Google App Engine Price Changes Say About the Future of Web Architecture
topicId topicWeight
[(0, 0.162), (1, 0.063), (2, -0.032), (3, 0.044), (4, -0.094), (5, -0.066), (6, 0.083), (7, -0.121), (8, 0.036), (9, -0.154), (10, 0.001), (11, -0.056), (12, 0.088), (13, -0.076), (14, -0.094), (15, -0.021), (16, 0.048), (17, 0.045), (18, 0.022), (19, 0.031), (20, -0.0), (21, -0.005), (22, 0.008), (23, -0.008), (24, -0.058), (25, -0.03), (26, -0.062), (27, -0.036), (28, -0.015), (29, -0.047), (30, -0.026), (31, 0.035), (32, 0.02), (33, 0.054), (34, -0.06), (35, -0.013), (36, 0.008), (37, -0.049), (38, -0.023), (39, 0.005), (40, 0.047), (41, 0.067), (42, -0.021), (43, -0.003), (44, 0.012), (45, 0.01), (46, -0.02), (47, 0.025), (48, 0.019), (49, 0.072)]
simIndex simValue blogId blogTitle
same-blog 1 0.98340511 1543 high scalability-2013-11-05-10 Things You Should Know About AWS
Introduction: Authored by Chris Fregly : Former Netflix Streaming Platform Engineer, AWS Certified Solution Architect and Purveyor of fluxcapacitor.com. Ahead of the upcoming 2nd annual re:Invent conference, inspired by Simone Brunozzi’s recent presentation at an AWS Meetup in San Francisco, and collected from a few of my recent Fluxcapacitor.com consulting engagements, I’ve compiled a list of 10 useful time and clock-tick saving tips about AWS. 1) Query AWS resource metadata Can’t remember the EBS-Optimized IO throughput of your c1.xlarge cluster? How about the size limit of an S3 object on a single PUT? awsnow.info is the answer to all of your AWS-resource metadata questions. Interested in integrating awsnow.info with your application? You’re in luck. There’s now a REST API , as well! Note: These are default soft limits and will vary by account. 2) Tame your S3 buckets Delete an entire S3 bucket with a single CLI command:
2 0.87049574 1347 high scalability-2012-10-25-Not All Regions are Created Equal - South America Es Bueno
Introduction: Rodrigo Campos shared some interesting benchmark results for AWS instances in the South America Region (SĂŁo Paulo) and US East Region (North Virginia). He summarized the results in this thread on the Guerrilla Capacity Planning list: The same instance type shows a different behavior depending on the region that it is running, this is particularly critical if you depend on multiple regions for disaster recovery or geographical load balancing Generally speaking performance is better and more consistent in the South America region when compared to Virginia, this is probably due to the fact that SA region was the latest to be deployed. Maybe the SA datacenter uses new server models or it is just underutilized, but this is a wild guess Write performance for the medium instance type in Virginia abruptly decays, dropping from almost 400 call/s to something around 300 calls/s, this is not very clear in the scatter plot but if you draw a time-based chart you can clearly see this pa
3 0.82843351 1286 high scalability-2012-07-18-Strategy: Kill Off Multi-tenant Instances with High CPU Stolen Time
Introduction: Are all instances created equal? Perhaps because under multi-tenancy multiple virtual machines run on the same physical host, not all applications will run equally well on every instance. In that case it makes sense to measure and move to a better performing instance. That's the interesting idea from @botchagalupe : Imagine something like a "performance monkey" where an infrastructure is so bound that it can kill lower performing instances automatically. @adrianco says Netflix has throught of doing the same: We've looked at killing off multi-tenant instances that have high CPU stolen time... Related Articles Host server CPU utilization in Amazon EC2 cloud
4 0.82758814 812 high scalability-2010-04-19-Strategy: Order Two Mediums Instead of Two Smalls and the EC2 Buffet
Introduction: Vaibhav Puranik in Web serving in the cloud – our experiences with nginx and instance sizes describes their experience trying to maximum traffic and minimum their web serving costs on EC2. Initially they tested with two m1.small instance types and then they the switched to two c1.mediums instance types. The m1s are the standard instance types and the c1s are the high CPU instance types. Obviously the mediums have greater capability, but the cost difference was interesting: In the long term they will save money using the larger instances and not autoscaling. With the small instances, traffic bursts caused autoscaling to kick in. New instances were started in response to load. The instances woud be up for a short period of time and then spin down again. This constant churn costs a lot of money. Selecting the larger instance sizes, which are capable of handling the load without autoscaling, turn out to save money even though they are more expensive. Starting new instances also tak
5 0.79513872 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
Introduction: This is a guest post by Shawn Hsiao , Luke Massa , and Victor Luu . Shawn runs TripAdvisor ’s Technical Operations team, Luke and Victor interned on his team this past summer. This post is introduced by Andy Gelfond , TripAdvisor’s head of engineering. It's been a little over a year since our last post about the TripAdvisor architecture . It has been an exciting year. Our business and team continues to grow, we are now an independent public company, and we have continued to keep/scale our development process and culture as we have grown - we still run dozens of independent teams, and each team continues to work across the entire stack. All that has changed are the numbers: 56M visitors per month 350M+ pages requests a day 120TB+ of warehouse data running on a large Hadoop cluster, and quickly growing We also had a very successful college intern program that brought on over 60 interns this past summer, all who were quickly on boarded and doing the same kind of work a
6 0.78959286 1058 high scalability-2011-06-13-Automation on AWS with Ruby and Puppet
7 0.7846539 1343 high scalability-2012-10-18-Save up to 30% by Selecting Better Performing Amazon Instances
8 0.78318441 1165 high scalability-2011-12-28-Strategy: Guaranteed Availability Requires Reserving Instances in Specific Zones
9 0.76773602 1631 high scalability-2014-04-14-How do you even do anything without using EBS?
10 0.7395466 1353 high scalability-2012-11-01-Cost Analysis: TripAdvisor and Pinterest costs on the AWS cloud
11 0.73936594 1371 high scalability-2012-12-12-Pinterest Cut Costs from $54 to $20 Per Hour by Automatically Shutting Down Systems
12 0.71616399 1296 high scalability-2012-08-02-Strategy: Use Spare Region Capacity to Survive Availability Zone Failures
13 0.71429455 1398 high scalability-2013-02-04-Is Provisioned IOPS Better? Yes, it Delivers More Consistent and Higher Performance IO
14 0.7045297 881 high scalability-2010-08-16-Scaling an AWS infrastructure - Tools and Patterns
16 0.69902885 1121 high scalability-2011-09-21-5 Scalability Poisons and 3 Cloud Scalability Antidotes
17 0.69795966 1248 high scalability-2012-05-21-Pinterest Architecture Update - 18 Million Visitors, 10x Growth,12 Employees, 410 TB of Data
18 0.69109643 853 high scalability-2010-07-08-Cloud AWS Infrastructure vs. Physical Infrastructure
19 0.66661155 138 high scalability-2007-10-30-Feedblendr Architecture - Using EC2 to Scale
20 0.66228575 1434 high scalability-2013-04-03-5 Steps to Benchmarking Managed NoSQL - DynamoDB vs Cassandra
topicId topicWeight
[(1, 0.125), (2, 0.167), (3, 0.011), (10, 0.153), (13, 0.011), (22, 0.158), (30, 0.038), (40, 0.036), (47, 0.013), (61, 0.034), (77, 0.015), (79, 0.093), (85, 0.021), (94, 0.037)]
simIndex simValue blogId blogTitle
same-blog 1 0.93355298 1543 high scalability-2013-11-05-10 Things You Should Know About AWS
Introduction: Authored by Chris Fregly : Former Netflix Streaming Platform Engineer, AWS Certified Solution Architect and Purveyor of fluxcapacitor.com. Ahead of the upcoming 2nd annual re:Invent conference, inspired by Simone Brunozzi’s recent presentation at an AWS Meetup in San Francisco, and collected from a few of my recent Fluxcapacitor.com consulting engagements, I’ve compiled a list of 10 useful time and clock-tick saving tips about AWS. 1) Query AWS resource metadata Can’t remember the EBS-Optimized IO throughput of your c1.xlarge cluster? How about the size limit of an S3 object on a single PUT? awsnow.info is the answer to all of your AWS-resource metadata questions. Interested in integrating awsnow.info with your application? You’re in luck. There’s now a REST API , as well! Note: These are default soft limits and will vary by account. 2) Tame your S3 buckets Delete an entire S3 bucket with a single CLI command:
Introduction: The story of driving the golden spike to symbolize the completion of the transcontinental railroad is famous in the US. What is not so well known is the story of how it also foreshadowed changes to come as an early version of both the Internet and the Internet of Things. But that was 1869, how can that possibly be? Telegraph as Internet First, let's establish the telegraph and cable systems was an early version of an Internet. As railroad tracks were being laid a transcontental telegraph system was also being constructed. Telegraph lines were installed parallel to the tracks making instant communication available across the continent, faster than any horse could ride. With the transalantic cable system information could quickly span continents in minutes: The miles of American telegraph grew from 40 in 1846 to 12,000 in 1850 to 23,000 in 1852. In Europe it increased from 2,000 in 1849 to 110,000 in 1869. The cost of sending 10 words was $1.55 in 1850, $1 in 1870, 40
3 0.85765743 792 high scalability-2010-03-10-How FarmVille Scales - The Follow-up
Introduction: Several readers had follow-up questions in response to How FarmVille Scales to Harvest 75 Million Players a Month . Here are Luke's response to those questions (and a few of mine). How does social networking makes things easier or harder? The primary interesting aspect of social networking games is how you wind up with a graph of connected users who need to be access each other's data on a frequent basis. This makes the overall dataset difficult if not impossible to partition. What are examples of the Facebook calls you try to avoid and how they impact game play? We can make a call for facebook friend data to retrieve information about your friends playing the game. Normally, we show a friend ladder at the bottom of the game that shows friend information, including name and facebook photo. Can you say where your cache is, what form it takes, and how much cached there is? Do you have a peering relationship with Facebook, as one might expect at that bandwidth?
4 0.85334712 1585 high scalability-2014-01-24-Stuff The Internet Says On Scalability For January 24th, 2014
Introduction: Hey, it's HighScalability time: Gorgeous image from Scientific American's Your Brain by the Numbers Quotable Quotes: @jezhumble : Google does everything off trunk despite 10k devs across 40 offices. @KentLangley : "in 2016. When it goes online, the SKA is expected to produce 700 terabytes of data each day" Jonathan Marks : It's actually a talk about how NOT to be creative. And what he [John Cleese] describes is the way most international broadcasters operated for most of their existence. They were content factories, slave to an artificial transmission schedule. Because they didn't take time to be creative, then ended up sounding like a tape machine. They were run by a computer algorithm. Not a human soul. There was never room for a creative pause. Routine was the solution. And that's creativities biggest enemy. 40% better single-threaded performance in MariaDB . Using perf, cache misses were found and the fix was using the righ
5 0.84595722 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
Introduction: This is a guest post by Shawn Hsiao , Luke Massa , and Victor Luu . Shawn runs TripAdvisor ’s Technical Operations team, Luke and Victor interned on his team this past summer. This post is introduced by Andy Gelfond , TripAdvisor’s head of engineering. It's been a little over a year since our last post about the TripAdvisor architecture . It has been an exciting year. Our business and team continues to grow, we are now an independent public company, and we have continued to keep/scale our development process and culture as we have grown - we still run dozens of independent teams, and each team continues to work across the entire stack. All that has changed are the numbers: 56M visitors per month 350M+ pages requests a day 120TB+ of warehouse data running on a large Hadoop cluster, and quickly growing We also had a very successful college intern program that brought on over 60 interns this past summer, all who were quickly on boarded and doing the same kind of work a
6 0.84386134 1046 high scalability-2011-05-23-Evernote Architecture - 9 Million Users and 150 Million Requests a Day
7 0.84296477 1635 high scalability-2014-04-21-This is why Microsoft won. And why they lost.
8 0.84170061 1371 high scalability-2012-12-12-Pinterest Cut Costs from $54 to $20 Per Hour by Automatically Shutting Down Systems
9 0.84148616 1353 high scalability-2012-11-01-Cost Analysis: TripAdvisor and Pinterest costs on the AWS cloud
10 0.84081119 1621 high scalability-2014-03-28-Stuff The Internet Says On Scalability For March 28th, 2014
11 0.83798712 1090 high scalability-2011-08-01-Peecho Architecture - scalability on a shoestring
12 0.83761382 1521 high scalability-2013-09-23-Salesforce Architecture - How they Handle 1.3 Billion Transactions a Day
13 0.8357318 1645 high scalability-2014-05-09-Stuff The Internet Says On Scalability For May 9th, 2014
14 0.83069909 491 high scalability-2009-01-13-Product: Gearman - Open Source Message Queuing System
15 0.82766169 774 high scalability-2010-02-08-How FarmVille Scales to Harvest 75 Million Players a Month
16 0.82616764 1068 high scalability-2011-06-27-TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data
17 0.82599735 257 high scalability-2008-02-22-Kevin's Great Adventures in SSDland
18 0.82593679 767 high scalability-2010-01-27-Hot Scalability Links for January 28 2010
19 0.82503223 142 high scalability-2007-11-05-Strategy: Diagonal Scaling - Don't Forget to Scale Out AND Up
20 0.8222968 1369 high scalability-2012-12-10-Switch your databases to Flash storage. Now. Or you're doing it wrong.