high_scalability high_scalability-2012 high_scalability-2012-1246 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: In Zen And The Art Of Scaling - A Koan And Epigram Approach , Russell Sullivan offered an interesting conjecture: there are 20 classic bottlenecks. This sounds suspiciously like the idea that there only 20 basic story plots . And depending on how you chunkify things, it may be true, but in practice we all know bottlenecks come in infinite flavors, all tasting of sour and ash. One day Aurelien Broszniowski from Terracotta emailed me his list of bottlenecks, we cc’ed Russell in on the conversation, he gave me his list, I have a list, and here’s the resulting stone soup. Russell said this is his “I wish I knew when I was younger" list and I think that’s an enriching way to look at it. The more experience you have, the more different types of projects you tackle, the more lessons you’ll be able add to a list like this. So when you read this list, and when you make your own, you are stepping through years of accumulated experience and more than a little frustration, but in ea
sentIndex sentText sentNum sentScore
1 This sounds suspiciously like the idea that there only 20 basic story plots . [sent-2, score-0.181]
2 And depending on how you chunkify things, it may be true, but in practice we all know bottlenecks come in infinite flavors, all tasting of sour and ash. [sent-3, score-0.216]
3 One day Aurelien Broszniowski from Terracotta emailed me his list of bottlenecks, we cc’ed Russell in on the conversation, he gave me his list, I have a list, and here’s the resulting stone soup. [sent-4, score-0.278]
4 Russell said this is his “I wish I knew when I was younger" list and I think that’s an enriching way to look at it. [sent-5, score-0.19]
5 The more experience you have, the more different types of projects you tackle, the more lessons you’ll be able add to a list like this. [sent-6, score-0.19]
6 So when you read this list, and when you make your own, you are stepping through years of accumulated experience and more than a little frustration, but in each there is a story worth grokking. [sent-7, score-0.26]
7 Event driven programming: callback complexity, how-to-store-state-in-function-calls, etc. [sent-11, score-0.086]
8 Lack of profiling, lack of tracing, lack of logging One piece can't scale, SPOF, non horizontally scalable, etc. [sent-14, score-0.192]
9 Stateful apps Bad design : The developers create an app which runs fine on their computer. [sent-17, score-0.144]
10 Not utilising the browser's cache enough Byte code caches (e. [sent-23, score-0.253]
11 This spans so much: snappy for network I/O, column DBs run algorithms directly on compressed data, etc. [sent-28, score-0.094]
12 Then there are techniques to not destroy your TLB. [sent-29, score-0.081]
13 The most important idea is to have a firm grasp on computer architecture in terms of CPUs multi-core, L1/L2, shared L3, NUMA RAM, data transfer bandwidth/latency from DRAM to chip, DRAM caches DiskPages, DirtyPages, TCP packets travel thru CPU<->DRAM<->NIC. [sent-30, score-0.318]
14 CPU: CPU overload Context switches -> too many threads on a core, bad luck w/ the linux scheduler, too many system calls, etc. [sent-31, score-0.183]
wordName wordTfidf (topN-words)
[('russell', 0.204), ('dram', 0.199), ('list', 0.19), ('disk', 0.167), ('caches', 0.145), ('fine', 0.144), ('swap', 0.138), ('tasting', 0.108), ('sour', 0.108), ('andreas', 0.108), ('saturation', 0.108), ('utilising', 0.108), ('taking', 0.105), ('etags', 0.102), ('gzipping', 0.102), ('linux', 0.099), ('thomson', 0.097), ('suspiciously', 0.097), ('descriptor', 0.097), ('fsync', 0.097), ('deadlocks', 0.097), ('frustration', 0.097), ('cpus', 0.096), ('lack', 0.096), ('snappy', 0.094), ('zappos', 0.094), ('malloc', 0.094), ('flushing', 0.091), ('thru', 0.091), ('younger', 0.091), ('irq', 0.091), ('stepping', 0.088), ('conjecture', 0.088), ('emailed', 0.088), ('thrashing', 0.088), ('accumulated', 0.088), ('filling', 0.086), ('heavyweight', 0.086), ('callback', 0.086), ('flavors', 0.086), ('brendan', 0.086), ('threads', 0.084), ('fluctuations', 0.084), ('story', 0.084), ('maxed', 0.082), ('spof', 0.082), ('cliff', 0.082), ('waits', 0.082), ('grasp', 0.082), ('destroy', 0.081)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000002 1246 high scalability-2012-05-16-Big List of 20 Common Bottlenecks
Introduction: In Zen And The Art Of Scaling - A Koan And Epigram Approach , Russell Sullivan offered an interesting conjecture: there are 20 classic bottlenecks. This sounds suspiciously like the idea that there only 20 basic story plots . And depending on how you chunkify things, it may be true, but in practice we all know bottlenecks come in infinite flavors, all tasting of sour and ash. One day Aurelien Broszniowski from Terracotta emailed me his list of bottlenecks, we cc’ed Russell in on the conversation, he gave me his list, I have a list, and here’s the resulting stone soup. Russell said this is his “I wish I knew when I was younger" list and I think that’s an enriching way to look at it. The more experience you have, the more different types of projects you tackle, the more lessons you’ll be able add to a list like this. So when you read this list, and when you make your own, you are stepping through years of accumulated experience and more than a little frustration, but in ea
2 0.1638201 1319 high scalability-2012-09-10-Russ’ 10 Ingredient Recipe for Making 1 Million TPS on $5K Hardware
Introduction: My name is Russell Sullivan , I am the author of AlchemyDB: a highly flexible NoSQL/SQL/DocumentStore/GraphDB-datastore built on top of redis. I have spent the last several years trying to find a way to sanely house multiple datastore-genres under one roof while (almost paradoxically) pushing performance to its limits. I recently joined the NoSQL company Aerospike (formerly Citrusleaf) with the goal of incrementally grafting AlchemyDB’s flexible data-modeling capabilities onto Aerospike’s high-velocity horizontally-scalable key-value data-fabric. We recently completed a peak-performance TPS optimization project : starting at 200K TPS, pushing to the recent community edition launch at 500K TPS, and finally arriving at our 2012 goal: 1M TPS on $5K hardware . Getting to one million over-the-wire client-server database-requests per-second on a single machine costing $5K is a balance between trimming overhead on many axes and using a shared nothing architecture to i
3 0.13128056 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
Introduction: We are on the edge of two potent technological changes: Clouds and Memory Based Architectures. This evolution will rip open a chasm where new players can enter and prosper. Google is the master of disk. You can't beat them at a game they perfected. Disk based databases like SimpleDB and BigTable are complicated beasts, typical last gasp products of any aging technology before a change. The next era is the age of Memory and Cloud which will allow for new players to succeed. The tipping point will be soon. Let's take a short trip down web architecture lane: It's 1993: Yahoo runs on FreeBSD, Apache, Perl scripts and a SQL database It's 1995: Scale-up the database. It's 1998: LAMP It's 1999: Stateless + Load Balanced + Database + SAN It's 2001: In-memory data-grid. It's 2003: Add a caching layer. It's 2004: Add scale-out and partitioning. It's 2005: Add asynchronous job scheduling and maybe a distributed file system. It's 2007: Move it all into the cloud. It's 2008: C
4 0.12609407 1199 high scalability-2012-02-27-Zen and the Art of Scaling - A Koan and Epigram Approach
Introduction: This is a guest post derived from an email conversation with Russell Sullivan , a computer architect and creator of Alchemy Database, A Hybrid RDBMS/NOSQL-Datastore. Russell (AKA Jak Sprats) has been pondering, considering, and implementing distributed databases for many years. In a recent email conversation he shared 44 of the lessons he has learned from developing the infrastructure for high performance / highly scalable systems. Some are well known, some are debatable, and some obviously result from a deep experience that is worth learning from: There are maybe 20 classic bottlenecks (CPU, NIC overload, memory fragmentation, disk seeks, swap, thread deadlock, packet loss, etc.), have a basic understanding of them, because each is a dark tunnel, and you need a specialised flashlight for each. The true style of scalable architecture is rooted in the nature of bottlenecks. I always talk about commutative operations on a sharded relational model, and I figure if that i
Introduction: Now that we have the C10K concurrent connection problem licked, how do we level up and support 10 million concurrent connections? Impossible you say. Nope, systems right now are delivering 10 million concurrent connections using techniques that are as radical as they may be unfamiliar. To learn how it’s done we turn to Robert Graham , CEO of Errata Security, and his absolutely fantastic talk at Shmoocon 2013 called C10M Defending The Internet At Scale . Robert has a brilliant way of framing the problem that I’ve never heard of before. He starts with a little bit of history, relating how Unix wasn’t originally designed to be a general server OS, it was designed to be a control system for a telephone network. It was the telephone network that actually transported the data so there was a clean separation between the control plane and the data plane. The problem is we now use Unix servers as part of the data plane , which we shouldn’t do at all. If we were des
6 0.11430699 1118 high scalability-2011-09-19-Big Iron Returns with BigMemory
7 0.11008038 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
8 0.10745703 1652 high scalability-2014-05-21-9 Principles of High Performance Programs
9 0.10476514 174 high scalability-2007-12-05-Product: Tugela Cache
10 0.1038764 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase
11 0.1023321 859 high scalability-2010-07-14-DynaTrace's Top 10 Performance Problems taken from Zappos, Monster, Thomson and Co
12 0.10143046 459 high scalability-2008-12-03-Java World Interview on Scalability and Other Java Scalability Secrets
13 0.10033196 1551 high scalability-2013-11-20-How Twitter Improved JVM Performance by Reducing GC and Faster Memory Allocation
14 0.099228851 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
15 0.099122033 1177 high scalability-2012-01-19-Is it time to get rid of the Linux OS model in the cloud?
16 0.098609105 1247 high scalability-2012-05-18-Stuff The Internet Says On Scalability For May 18, 2012
17 0.09756422 1475 high scalability-2013-06-13-Busting 4 Modern Hardware Myths - Are Memory, HDDs, and SSDs Really Random Access?
19 0.095169999 1471 high scalability-2013-06-06-Paper: Memory Barriers: a Hardware View for Software Hackers
20 0.093873955 1508 high scalability-2013-08-28-Sean Hull's 20 Biggest Bottlenecks that Reduce and Slow Down Scalability
topicId topicWeight
[(0, 0.176), (1, 0.098), (2, -0.023), (3, -0.014), (4, -0.01), (5, 0.047), (6, 0.048), (7, 0.06), (8, -0.083), (9, -0.03), (10, -0.042), (11, -0.055), (12, 0.033), (13, 0.042), (14, -0.08), (15, -0.081), (16, 0.002), (17, -0.002), (18, -0.023), (19, 0.015), (20, -0.045), (21, -0.013), (22, 0.007), (23, 0.054), (24, -0.032), (25, -0.011), (26, 0.041), (27, -0.038), (28, -0.009), (29, 0.024), (30, -0.01), (31, 0.0), (32, 0.03), (33, -0.025), (34, -0.011), (35, 0.031), (36, 0.004), (37, 0.013), (38, 0.016), (39, 0.024), (40, -0.003), (41, 0.002), (42, 0.039), (43, -0.019), (44, 0.008), (45, 0.035), (46, -0.01), (47, -0.021), (48, -0.005), (49, 0.045)]
simIndex simValue blogId blogTitle
same-blog 1 0.95917416 1246 high scalability-2012-05-16-Big List of 20 Common Bottlenecks
Introduction: In Zen And The Art Of Scaling - A Koan And Epigram Approach , Russell Sullivan offered an interesting conjecture: there are 20 classic bottlenecks. This sounds suspiciously like the idea that there only 20 basic story plots . And depending on how you chunkify things, it may be true, but in practice we all know bottlenecks come in infinite flavors, all tasting of sour and ash. One day Aurelien Broszniowski from Terracotta emailed me his list of bottlenecks, we cc’ed Russell in on the conversation, he gave me his list, I have a list, and here’s the resulting stone soup. Russell said this is his “I wish I knew when I was younger" list and I think that’s an enriching way to look at it. The more experience you have, the more different types of projects you tackle, the more lessons you’ll be able add to a list like this. So when you read this list, and when you make your own, you are stepping through years of accumulated experience and more than a little frustration, but in ea
2 0.90139085 1471 high scalability-2013-06-06-Paper: Memory Barriers: a Hardware View for Software Hackers
Introduction: It's not often you get so enthusiastic a recommendation for a paper as Sergio Bossa gives Memory Barriers: a Hardware View for Software Hackers : If you only want to read one piece about CPUs architecture, cache coherency and memory barriers, make it this one. It is a clear and well written article. It even has a quiz. What's it about? So what possessed CPU designers to cause them to inflict memory barriers on poor unsuspecting SMP software designers? In short, because reordering memory references allows much better performance, and so memory barriers are needed to force ordering in things like synchronization primitives whose correct operation depends on ordered memory references. Getting a more detailed answer to this question requires a good understanding of how CPU caches work, and especially what is required to make caches really work well. The following sections: present the structure of a cache, describe how cache-coherency protocols ensure that CPUs agree on t
3 0.87190253 1652 high scalability-2014-05-21-9 Principles of High Performance Programs
Introduction: Arvid Norberg on the libtorrent blog has put together an excellent list of principles of high performance programs , obviously derived from hard won experience programming on bittorrent: Two fundamental causes of performance problems: Memory Latency . A big performance problem on modern computers is the latency of SDRAM. The CPU waits idle for a read from memory to come back. Context Switching . When a CPU switches context "the memory it will access is most likely unrelated to the memory the previous context was accessing. This often results in significant eviction of the previous cache, and requires the switched-to context to load much of its data from RAM, which is slow." Rules to help balance the forces of evil: Batch work . Avoid context switching by batching work. For example, there are vector versions of system calls like writev() and readv() that operate on more than one item per call. An implication is that you want to merge as many writes as possible.
4 0.84149021 1582 high scalability-2014-01-20-8 Ways Stardog Made its Database Insanely Scalable
Introduction: Stardog makes a commercial graph database that is a great example of what can be accomplished with a scale-up strategy on BigIron. In a recent article StarDog described how they made their new 2.1 release insanely scalable, improving query scalability by about 3 orders of magnitude and it can now handle 50 billion triples on a $10,000 server with 32 cores and 256 GB RAM. It can also load 20B datasets at 300,000 triples per second. What did they do that you can also do? Avoid locks by using non-blocking algorithms and data structures . For example, moving from BitSet to ConcurrentLinkedQueue. Use ThreadLocal aggressively to reduce thread contention and avoid synchronization . Batch LRU evictions in a single thread . Triggered by several LRU caches becoming problematic when evictions were being swamped by additions. Downside is batching increases memory pressure and GC times. Move to SHA1 for hashing URIs, bnodes, and literal values . Making hash collisions nearly imp
5 0.81072843 1003 high scalability-2011-03-14-6 Lessons from Dropbox - One Million Files Saved Every 15 minutes
Introduction: Dropbox saves one million files every 15 minutes, more tweets than even Twitterers tweet. That mind blowing statistic was revealed by Rian Hunter, a Dropbox Engineer, in his presentation How Dropbox Did It and How Python Helped at PyCon 2011. The first part of the presentation is some Dropbox lore, origin stories and other foundational myths. We learn that Dropbox is a startup company located in San Francisco that has probably one of the most popular file synchronization and sharing tools in the world, shipping Python on the desktop and supporting millions of users and growing every day . About half way through the talk turns technical. Not a lot of info on how Dropbox handles this massive scale was dropped, but there were a number of good lessons to ponder: Use Python 99.9 % of their code is in Python. Used on the server backend; desktop client, website controller logic, API backend, and analytics. Can't use Python on the Android due to memory constraints. Runs
6 0.80905312 1475 high scalability-2013-06-13-Busting 4 Modern Hardware Myths - Are Memory, HDDs, and SSDs Really Random Access?
7 0.80086792 1237 high scalability-2012-05-02-12 Ways to Increase Throughput by 32X and Reduce Latency by 20X
8 0.78772664 1536 high scalability-2013-10-23-Strategy: Use Linux Taskset to Pin Processes or Let the OS Schedule It?
9 0.7832818 1407 high scalability-2013-02-15-Stuff The Internet Says On Scalability For February 15, 2013
10 0.77792251 1314 high scalability-2012-08-30-Dramatically Improving Performance by Debugging Brutally Complex Prolems
11 0.77522635 1462 high scalability-2013-05-22-Strategy: Stop Using Linked-Lists
12 0.77334064 1387 high scalability-2013-01-15-More Numbers Every Awesome Programmer Must Know
13 0.77277774 505 high scalability-2009-02-01-More Chips Means Less Salsa
14 0.77152038 1319 high scalability-2012-09-10-Russ’ 10 Ingredient Recipe for Making 1 Million TPS on $5K Hardware
15 0.76077914 1588 high scalability-2014-01-31-Stuff The Internet Says On Scalability For January 31st, 2014
16 0.75372517 1467 high scalability-2013-05-30-Google Finds NUMA Up to 20% Slower for Gmail and Websearch
17 0.75286537 914 high scalability-2010-10-04-Paper: An Analysis of Linux Scalability to Many Cores
18 0.75166124 1456 high scalability-2013-05-13-The Secret to 10 Million Concurrent Connections -The Kernel is the Problem, Not the Solution
19 0.75104547 701 high scalability-2009-09-10-When optimizing - don't forget the Java Virtual Machine (JVM)
20 0.7505514 1218 high scalability-2012-03-29-Strategy: Exploit Processor Affinity for High and Predictable Performance
topicId topicWeight
[(1, 0.064), (2, 0.258), (10, 0.095), (30, 0.036), (47, 0.021), (56, 0.012), (59, 0.038), (61, 0.087), (63, 0.17), (77, 0.025), (79, 0.085), (85, 0.027), (94, 0.014)]
simIndex simValue blogId blogTitle
same-blog 1 0.92408997 1246 high scalability-2012-05-16-Big List of 20 Common Bottlenecks
Introduction: In Zen And The Art Of Scaling - A Koan And Epigram Approach , Russell Sullivan offered an interesting conjecture: there are 20 classic bottlenecks. This sounds suspiciously like the idea that there only 20 basic story plots . And depending on how you chunkify things, it may be true, but in practice we all know bottlenecks come in infinite flavors, all tasting of sour and ash. One day Aurelien Broszniowski from Terracotta emailed me his list of bottlenecks, we cc’ed Russell in on the conversation, he gave me his list, I have a list, and here’s the resulting stone soup. Russell said this is his “I wish I knew when I was younger" list and I think that’s an enriching way to look at it. The more experience you have, the more different types of projects you tackle, the more lessons you’ll be able add to a list like this. So when you read this list, and when you make your own, you are stepping through years of accumulated experience and more than a little frustration, but in ea
2 0.92300719 193 high scalability-2007-12-26-Finding an excellent LAMP developer
Introduction: Hi... I have this idea to start a really great and scalable website, and I am building it! So far I'm doing everything myself - coding, networking, architecture planning, everything. I haven't even gotten into the legal aspects yet....... It would be MUCH easier if I had a technical person to handle that end of the operation. I'm a good coder, but like Bill Gates at Harvard for Math, I'm not the very best. I'd like to FIND that very best person available, to handle the technical aspects. For worse or better, I don't presently know somebody who fits this bill. I've posted a bazillion ads on Craig's List, with no really qualified responses. I've put out feelers among my own network, same result. Not sure what else I can do. Shoestring budget, so it's sweat equity in the beginning. That can actually be a plus, as it forces people to focus. Any ideas about what else I can do, to attract the right person? Thanks Jason
3 0.91268349 940 high scalability-2010-11-12-Stuff the Internet Says on Scalability For November 12th, 2010
Introduction: Google – A Study In Scalability And A Little Systems Horse Sense . A nice summary by Krishna Sankar of a version of Jeff Dean's classic talk on Google Scalability given to Stanford's EE380 class . Quotable Quotes: @jkalucki : Getting just 100 servers to work together for the first time is so ridiculously complicated. Horizontal scaling doesn't scale. @simeons : Yahoo's scalability is drivem by lots of asynchronous processing. "You learn to love it." -- @rstata Yahoo's CTO The Economics of the Cloud: Dissecting a Must-Read White Paper by Bernard Golden. I love the depiction of the unseen and unfelt forces that nevertheless organize everything around them: After a brief introduction, the authors lay out a central thesis: despite initial concerns about shortcomings in new technology offerings, "historically, underlying economics have a much stronger impact on the direction and speed of disruptions, as technological challenges are resolved or overcome thro
4 0.88925314 1613 high scalability-2014-03-17-Intuitively Showing How To Scale a Web Application Using a Coffee Shop as an Example
Introduction: This is a guest repost by Sriram Devadas , Engineer at Vistaprint, Web platform group. A fun and well written analogy of how to scale web applications using a familiar coffee shop as an example. No coffee was harmed during the making of this post. I own a small coffee shop. My expense is proportional to resources 100 square feet of built up area with utilities, 1 barista, 1 cup coffee maker. My shop's capacity Serves 1 customer at a time, takes 3 minutes to brew a cup of coffee, a total of 5 minutes to serve a customer. Since my barista works without breaks and the German made coffee maker never breaks down, my shop's maximum throughput = 12 customers per hour. Web server Customers walk away during peak hours. We only serve one customer at a time. There is no space to wait. I upgrade shop. My new setup is better! Expenses Same area and utilities, 3 baristas, 2 cup coffee maker, 2 chairs Capacity 3 minutes to brew 2 cups of coffee, ~7 minutes to serv
5 0.86628634 999 high scalability-2011-03-04-Stuff The Internet Says On Scalability For March 4, 2011
Introduction: Submitted for your reading pleasure on this beautifully blue and sunny Friday... @Werner : Each day #AWS adds enough computing muscle to power one whole Amazon.com circa 2000, when it was a $2.8 billion business http://wv.ly/gMr8LQ Building servers to rule in hell. Datacenters spend a lot of energy on cooling down processors. Why can't they operate at higher temperatures? This is the proposition addressed by James Hamilton in Exploring the Limits of Datacenter Temprature and Datacenter Knowledge in What’s Next? Hotter Servers with ‘Gas Pedals’ . Quotable Quotes for 200 Watson: @jreichhold : One thing working at Twitter teaches me daily is that all scale is relative. What seemed impossible last year is now the daily case. @dannycast0nguay : If you’re concerned about scalability, any algorithm that forces you to run agreement will eventually become your bottleneck.—Werner Vogels @rael : No shortcut ever goes undetected by scale. @sr
6 0.86516345 1346 high scalability-2012-10-24-Saving Cash Using Less Cache - 90% Savings in the Caching Tier
7 0.85834771 1291 high scalability-2012-07-25-Vertical Scaling Ascendant - How are SSDs Changing Architectures?
8 0.85432374 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
9 0.85369134 306 high scalability-2008-04-21-The Search for the Source of Data - How SimpleDB Differs from a RDBMS
10 0.85188419 1425 high scalability-2013-03-18-Beyond Threads and Callbacks - Application Architecture Pros and Cons
11 0.85183924 1475 high scalability-2013-06-13-Busting 4 Modern Hardware Myths - Are Memory, HDDs, and SSDs Really Random Access?
12 0.85112 619 high scalability-2009-06-05-HotPads Shows the True Cost of Hosting on Amazon
13 0.84868288 1418 high scalability-2013-03-06-Low Level Scalability Solutions - The Aggregation Collection
14 0.8478595 1329 high scalability-2012-09-26-WordPress.com Serves 70,000 req-sec and over 15 Gbit-sec of Traffic using NGINX
15 0.84774345 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase
16 0.8461079 1010 high scalability-2011-03-24-Strategy: Disk Backup for Speed, Tape Backup to Save Your Bacon, Just Ask Google
18 0.84438306 714 high scalability-2009-10-02-HighScalability has Moved to Squarespace.com!
19 0.84409451 1429 high scalability-2013-03-25-AppBackplane - A Framework for Supporting Multiple Application Architectures
20 0.84400791 1017 high scalability-2011-04-06-Netflix: Run Consistency Checkers All the time to Fixup Transactions