high_scalability high_scalability-2012 high_scalability-2012-1172 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . Plan for the fact that everything you make is going to break. Design in layers that are independent and redundant. Everything is a Feature . Your application is a set of features created by a series of conscious choices made by considering trade-offs. Scale Out, Not Up . Purchasing more hardware is easier than coding and managing horizontal resources. Buy More Storage . Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. You’re Going to Do It Wrong . Be prepared to iterate on your ideas. You will make mistakes. Be prepared to re-write code and to quickly move on to the next idea. Please read the original article for a much more expansive treatment.
sentIndex sentText sentNum sentScore
1 Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . [sent-1, score-0.591]
2 Plan for the fact that everything you make is going to break. [sent-2, score-0.384]
3 Your application is a set of features created by a series of conscious choices made by considering trade-offs. [sent-5, score-0.915]
4 Purchasing more hardware is easier than coding and managing horizontal resources. [sent-7, score-0.557]
5 Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. [sent-9, score-0.414]
6 Be prepared to re-write code and to quickly move on to the next idea. [sent-13, score-0.63]
7 Please read the original article for a much more expansive treatment. [sent-14, score-0.327]
wordName wordTfidf (topN-words)
[('prepared', 0.339), ('expansive', 0.271), ('treatment', 0.252), ('peschka', 0.239), ('jeremiah', 0.229), ('theoriginal', 0.221), ('purchasing', 0.206), ('expectations', 0.203), ('conscious', 0.188), ('iterate', 0.177), ('iops', 0.161), ('coding', 0.143), ('considering', 0.143), ('horizontal', 0.141), ('fewer', 0.141), ('reach', 0.14), ('layers', 0.14), ('going', 0.137), ('drives', 0.134), ('success', 0.134), ('choices', 0.132), ('independent', 0.127), ('set', 0.118), ('smaller', 0.114), ('plan', 0.112), ('buy', 0.109), ('series', 0.108), ('numbers', 0.107), ('managing', 0.107), ('fact', 0.105), ('easier', 0.101), ('larger', 0.1), ('quickly', 0.09), ('created', 0.088), ('move', 0.081), ('case', 0.075), ('make', 0.074), ('faster', 0.073), ('made', 0.072), ('everything', 0.068), ('next', 0.068), ('features', 0.066), ('hardware', 0.065), ('design', 0.06), ('read', 0.056), ('great', 0.055), ('build', 0.052), ('code', 0.052), ('scalability', 0.047), ('large', 0.047)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
Introduction: Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . Plan for the fact that everything you make is going to break. Design in layers that are independent and redundant. Everything is a Feature . Your application is a set of features created by a series of conscious choices made by considering trade-offs. Scale Out, Not Up . Purchasing more hardware is easier than coding and managing horizontal resources. Buy More Storage . Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. You’re Going to Do It Wrong . Be prepared to iterate on your ideas. You will make mistakes. Be prepared to re-write code and to quickly move on to the next idea. Please read the original article for a much more expansive treatment.
2 0.14104052 877 high scalability-2010-08-12-Designing Web Applications for Scalability
Introduction: I can’t even count the number of times that I’ve heard this phrase: “don’t worry about scaling your web application, worry about visitor (or customer) acquisition.” My response to this is always that you don’t need to choose one or the other, you can do both! In this post, I’m going to go over some of the strategies I’ve used to architect web applications for scalability, right from the start of the design process, in such a way that I’m prepared to scale when I need to, but not forced into doing so before its necessary. Easing the transition from small scale to large scale can be made much easier by choosing the right technologies and implementing the right coding patterns up front. You can read the full store here .
3 0.10903938 49 high scalability-2007-07-30-allowed contributed
Introduction: buy cleocin
4 0.10763354 559 high scalability-2009-04-07-Six Lessons Learned Deploying a Large-scale Infrastructure in Amazon EC2
Introduction: Lessons learned from OpenX's large-scale deployment to Amazon EC2: Expect failures; what's more, embrace them Fully automate your infrastructure deployments Design your infrastructure so that it scales horizontally Establish clear measurable goals Be prepared to quickly identify and eliminate bottlenecks Play wack-a-mole for a while, until things get stable
5 0.082736343 1369 high scalability-2012-12-10-Switch your databases to Flash storage. Now. Or you're doing it wrong.
Introduction: This is a guest post by Brian Bulkowski , CTO and co-founder of Aerospike , a leading clustered NoSQL database, has worked in the area of high performance commodity systems since 1989. Why flash rules for databases The economics of flash memory are staggering. If you’re not using SSD, you are doing it wrong. Not quite true, but close. Some small applications fit entirely in memory – less than 100GB – great for in-memory solutions. There’s a place for rotational drives (HDD) in massive streaming analytics and petabytes of data. But for the vast space between, flash has become the only sensible option. For example, the Samsung 840 costs $180 for 250GB. The speed rating for this drive is rated by the manufacturer at 96,000 random 4K read IOPS, and 61,000 random 4K write IOPS. The Samsung 840 is not alone at this price performance. A 300GB Intel 320 is $450. An OCZ Vertex 4 256GB is $235, with the Intel being rated as slowest, but our internal testing showing
6 0.074709237 1398 high scalability-2013-02-04-Is Provisioned IOPS Better? Yes, it Delivers More Consistent and Higher Performance IO
7 0.07417383 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
8 0.07371214 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
9 0.073356479 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
10 0.070624486 727 high scalability-2009-10-25-Is Your Data Really Secured?
11 0.070583083 1117 high scalability-2011-09-16-Stuff The Internet Says On Scalability For September 16, 2011
12 0.06971927 10 high scalability-2007-07-15-Book: Building Scalable Web Sites
13 0.069621027 1588 high scalability-2014-01-31-Stuff The Internet Says On Scalability For January 31st, 2014
14 0.069057554 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
15 0.067633323 1640 high scalability-2014-04-30-10 Tips for Optimizing NGINX and PHP-fpm for High Traffic Sites
16 0.06541235 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
17 0.063811436 1451 high scalability-2013-05-03-Stuff The Internet Says On Scalability For May 3, 2013
18 0.063126042 1387 high scalability-2013-01-15-More Numbers Every Awesome Programmer Must Know
19 0.06220888 870 high scalability-2010-08-02-7 Scaling Strategies Facebook Used to Grow to 500 Million Users
20 0.061663732 248 high scalability-2008-02-13-What's your scalability plan?
topicId topicWeight
[(0, 0.097), (1, 0.052), (2, -0.016), (3, 0.024), (4, 0.009), (5, -0.028), (6, -0.016), (7, 0.001), (8, -0.002), (9, -0.032), (10, -0.021), (11, -0.007), (12, -0.006), (13, 0.039), (14, 0.008), (15, -0.017), (16, 0.032), (17, -0.01), (18, -0.029), (19, 0.033), (20, -0.005), (21, 0.003), (22, -0.008), (23, -0.015), (24, -0.026), (25, 0.002), (26, -0.016), (27, -0.032), (28, -0.028), (29, 0.035), (30, 0.018), (31, 0.036), (32, 0.045), (33, 0.013), (34, -0.028), (35, 0.024), (36, -0.021), (37, -0.0), (38, 0.011), (39, -0.057), (40, -0.005), (41, -0.005), (42, -0.0), (43, -0.03), (44, 0.001), (45, 0.001), (46, -0.0), (47, -0.007), (48, -0.024), (49, -0.036)]
simIndex simValue blogId blogTitle
same-blog 1 0.97192693 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
Introduction: Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . Plan for the fact that everything you make is going to break. Design in layers that are independent and redundant. Everything is a Feature . Your application is a set of features created by a series of conscious choices made by considering trade-offs. Scale Out, Not Up . Purchasing more hardware is easier than coding and managing horizontal resources. Buy More Storage . Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. You’re Going to Do It Wrong . Be prepared to iterate on your ideas. You will make mistakes. Be prepared to re-write code and to quickly move on to the next idea. Please read the original article for a much more expansive treatment.
Introduction: Update 2: Velocity 09: John Allspaw, 10+ Deploys Per Day: Dev and Ops Cooperation at Flickr . Insightful talk. Some highlights: Change is good if you can build tools and culture to lower the risk of change. Operations and developers need to become of one mind and respect each other. An automated infrastructure is the one tool you need most. Common source control. One step build. One step deploy. Don't be a pussy, deploy. Always ship trunk. Feature flags - don't branch code, make features runtime configurable in code. Dark launch - release data paths early without UI component. Shared metrics. Adaptive feedback to prioritize important features. IRC for communication for human context. Best solutions occur when dev and op work together and trust each other. Trust is earned by helping each other solve their problems. Look at what new features imply for operations, what can go wrong, and how to recover. Provide knobs and levers to help operations. Devs should have access to production
3 0.72690284 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
Introduction: This is a guest posting by Marty Abbott and Michael Fisher, authors of The Art of Scalability . I'm still reading their book and will have an interview with them a little later. If 2010 is the year that you’ve decided to kickoff your startup or if you’ve already got something off the ground and are expecting double or triple digit growth, this list is for you. We all want the attention of user s to achieve viral growth but as many can attest , too much attention can bring a startup to its knees. If you’ve used Twitter for any amount of time you’re sure to have seen the “Fail Whale”, which is so often seen that it has its own fan club . Take a look at the graph below from Compete.com showing Twitter’s unique visitors. One can argue that limitations in the product offering have as much to do with the flattening of growth over the past six months as does the availability , but it’s hard to beli
4 0.71447712 1384 high scalability-2013-01-09-The Story of How Turning Disk Into a Service Lead to a Deluge of Density
Introduction: We usually think of the wonderful advantages of service oriented architectures as a software thing, but it also applies to hardware. In Security Now 385 , that Doyen of Disk, Steve Gibson , tells the fascinating story (@ about 41:30) of how moving to a service oriented architecture in hard drives, modeling a drive as a linear stream of sectors, helped create the amazing high density disk drives we enjoy today. When drives switched to use the IDE (integrated drive electronics) interface, the controller function moved into the drive instead of the computer. No longer were low level drive signals moved across cables and into the motherboard. Now we just ask the drive for the desired sector and the drive takes care of it. This allowed manufacturers to do anything they wanted to behind the IDE interface. The drive stopped being dumb, it became smart, providing a sort of sector service. Density sky rocketed because there was no dependency on the computer. All the internals could co
Introduction: Here's a common situation and question from the mechanical-sympathy Google group by Avinash Agrawal on the black art of capacity planning: How to get started with sizing and capacity planning, assuming we don't know the software behavior and its completely new product to deal with? Gil Tene , Vice President of Technology and CTO & Co-Founder, wrote a very understandable and useful answer that is worth highlighting: Start with requirements. I see way too many "capacity planning" exercises that go off spending weeks measuring some irrelevant metrics about a system (like how many widgets per hour can this thing do) without knowing what they actually need it to do. There are two key sets of metrics to state here: the "how much" set and the "how bad" set: In the "How Much" part, you need to establish, based on expected business needs, Numbers for things (like connections, users, streams, transactions or messages per second) that you expect to interact with at the peak t
6 0.70085371 185 high scalability-2007-12-13-Is premature scalation a real disease?
7 0.70026273 1027 high scalability-2011-04-20-Packet Pushers: How to Build a Low Cost Data Center
8 0.69589734 142 high scalability-2007-11-05-Strategy: Diagonal Scaling - Don't Forget to Scale Out AND Up
9 0.69587696 777 high scalability-2010-02-15-Scaling Ambition at StackOverflow
10 0.68905377 1503 high scalability-2013-08-19-What can the Amazing Race to the South Pole Teach us About Startups?
11 0.68578696 1458 high scalability-2013-05-15-Lesson from Airbnb: Give Yourself Permission to Experiment with Non-scalable Changes
12 0.68243515 1506 high scalability-2013-08-23-Stuff The Internet Says On Scalability For August 23, 2013
13 0.68144161 877 high scalability-2010-08-12-Designing Web Applications for Scalability
14 0.67750949 1420 high scalability-2013-03-08-Stuff The Internet Says On Scalability For March 8, 2013
15 0.66721648 1534 high scalability-2013-10-18-Stuff The Internet Says On Scalability For October 18th, 2013
16 0.66282082 1235 high scalability-2012-04-27-Stuff The Internet Says On Scalability For April 27, 2012
17 0.66238594 1199 high scalability-2012-02-27-Zen and the Art of Scaling - A Koan and Epigram Approach
18 0.65784264 1410 high scalability-2013-02-20-Smart Companies Fail Because they Do Everything Right - Staying Alive to Scale
19 0.65536356 1244 high scalability-2012-05-11-Stuff The Internet Says On Scalability For May 11, 2012
20 0.65224999 407 high scalability-2008-10-10-The Art of Capacity Planning: Scaling Web Resources
topicId topicWeight
[(2, 0.324), (10, 0.053), (61, 0.111), (62, 0.129), (77, 0.043), (94, 0.212)]
simIndex simValue blogId blogTitle
same-blog 1 0.93456781 1172 high scalability-2012-01-10-A Perfect Fifth of Notes on Scalability
Introduction: Jeremiah Peschka with a great a set of Notes on Scalability , just in case you do reach your wildest expectations of success: Build it to Break . Plan for the fact that everything you make is going to break. Design in layers that are independent and redundant. Everything is a Feature . Your application is a set of features created by a series of conscious choices made by considering trade-offs. Scale Out, Not Up . Purchasing more hardware is easier than coding and managing horizontal resources. Buy More Storage . Large numbers of smaller, faster drives have more IOPS than fewer, larger drives. You’re Going to Do It Wrong . Be prepared to iterate on your ideas. You will make mistakes. Be prepared to re-write code and to quickly move on to the next idea. Please read the original article for a much more expansive treatment.
2 0.87022865 1023 high scalability-2011-04-14-Strategy: Cache Application Start State to Reduce Spin-up Times
Introduction: Using this strategy, Valyala, a commenter on Are Long VM Instance Spin-Up Times In The Cloud Costing You Money? , was able to reduce their GAE application start-up times from 15 seconds down to to 1.5 seconds: Spin-up time for newly added Google AppEngine instances can be reduced using initial state caching. Usually the majority of spin-up time for the newly created GAE instance is spent in the pre-populating of the initial state, which is created from many data pieces loaded from slow data sources such as GAE's datastore. If the initial state is identical among GAE instances, then the entire state can be serialized and stored in a shared memory (either in the memcache or in the datastore) by the first created instance, so newly created instances could load and quickly unserialize the state from a single blob loaded from shared memory instead of spending a lot of time for creation of the state from multiple data pieces loaded from the datastore. I reduced spin-up time for new in
3 0.84444553 1084 high scalability-2011-07-22-Stuff The Internet Says On Scalability For July 22, 2011
Introduction: Submitted for your scaling pleasure: Google's PageRank involves 500 million variables and 2 billion terms . SeaMicro Packs 768 Cores Into its Atom Server . Twitter: 1 Billion Items Delivered A Day Is Nice, Google+. We Do 350 Billion. Potent quotables: @merv - Does elastic scalability matter? Ask Apple about 1 million e-transactions in a day. $30M worth of multi-gig downloads that must work. @lmacvittie - Cloud has shifted the focus of scalability from applications to architecture. @bartbohn - Love the phrase "anarchic scalability" by Roy Fielding @iAjayMe - Programming: I have come to the conclusion, if you want to do something right the first time (scalability,performance) write it in C++ @mreferre - Interesting discussion between @jamesurquhart and @lmacvittie about PaaS/App scalability (I think). Need google translator though... @krisajenkins - My deal with #nosql: if I'm giving up transactions, it has to buy me no SPOF. @c3iq - "Hundred
4 0.84355581 376 high scalability-2008-09-03-MapReduce framework Disco
Introduction: Disco is an open-source implementation of the MapReduce framework for distributed computing. It was started at Nokia Research Center as a lightweight framework for rapid scripting of distributed data processing tasks. The Disco core is written in Erlang. The MapReduce jobs in Disco are natively described as Python programs, which makes it possible to express complex algorithmic and data processing tasks often only in tens of lines of code.
5 0.82850921 177 high scalability-2007-12-08-thesimsonstage.ea.com
Introduction: Cou l d anyone make an overv i ew of thesimsonstage.ea.com arch i tecture, i.e. some stats, w i ch techno l ogy thay use, how they imp l ement karaoke f l ash-based p l ayer, wh i ch med i a server they use, how many bandw i d t h does it need, etc. Any informat i on wi l l be he l pful. Thanks.
6 0.82785648 575 high scalability-2009-04-21-Thread Pool Engine in MS CLR 4, and Work-Stealing scheduling algorithm
7 0.82160771 752 high scalability-2009-12-17-Oracle and IBM databases: Disk-based vs In-memory databases
8 0.82131261 342 high scalability-2008-06-08-Search fast in million rows
10 0.81586635 545 high scalability-2009-03-19-Product: Redis - Not Just Another Key-Value Store
11 0.815238 1601 high scalability-2014-02-25-Peter Norvig's 9 Master Steps to Improving a Program
12 0.81499058 437 high scalability-2008-11-03-How Sites are Scaling Up for the Election Night Crush
13 0.81437558 1296 high scalability-2012-08-02-Strategy: Use Spare Region Capacity to Survive Availability Zone Failures
14 0.81318194 970 high scalability-2011-01-06-BankSimple Mini-Architecture - Using a Next Generation Toolchain
15 0.81221503 1223 high scalability-2012-04-06-Stuff The Internet Says On Scalability For April 6, 2012
16 0.81107533 1174 high scalability-2012-01-13-Stuff The Internet Says On Scalability For January 13, 2012
17 0.80953795 1305 high scalability-2012-08-16-Paper: A Provably Correct Scalable Concurrent Skip List
18 0.80863535 863 high scalability-2010-07-22-How can we spark the movement of research out of the Ivory Tower and into production?
19 0.80346322 556 high scalability-2009-04-05-At Some Point the Cost of Servers Outweighs the Cost of Programmers
20 0.80284506 907 high scalability-2010-09-23-Working With Large Data Sets