high_scalability high_scalability-2011 high_scalability-2011-1116 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: In It's Time for Low Latency Stephen Rumble et al. explore the idea that it's time to rearchitect our stack to live in the modern era of low-latency datacenter instead of high-latency WANs. The implications for program architectures will be revolutionary . Luiz André Barroso , Distinguished Engineer at Google, sees ultra low latency as a way to make computer resources, to be as much as possible, fungible, that is they are interchangeable and location independent, effectively turning a datacenter into single computer. Abstract from the paper: The operating systems community has ignored network latency for too long. In the past, speed-of-light delays in wide area networks and unoptimized network hardware have made sub-100µs round-trip times impossible. However, in the next few years datacenters will be deployed with low-latency Ethernet. Without the burden of propagation delays in the datacenter campus and network delays in the Ethernet devices, it will be up to us to finish
sentIndex sentText sentNum sentScore
1 In It's Time for Low Latency Stephen Rumble et al. [sent-1, score-0.124]
2 explore the idea that it's time to rearchitect our stack to live in the modern era of low-latency datacenter instead of high-latency WANs. [sent-2, score-0.6]
3 The implications for program architectures will be revolutionary . [sent-3, score-0.094]
4 Luiz André Barroso , Distinguished Engineer at Google, sees ultra low latency as a way to make computer resources, to be as much as possible, fungible, that is they are interchangeable and location independent, effectively turning a datacenter into single computer. [sent-4, score-1.249]
5 Abstract from the paper: The operating systems community has ignored network latency for too long. [sent-5, score-0.451]
6 In the past, speed-of-light delays in wide area networks and unoptimized network hardware have made sub-100µs round-trip times impossible. [sent-6, score-0.524]
7 However, in the next few years datacenters will be deployed with low-latency Ethernet. [sent-7, score-0.15]
8 Without the burden of propagation delays in the datacenter campus and network delays in the Ethernet devices, it will be up to us to finish the job and see this benefit through to applications. [sent-8, score-1.427]
9 We argue that OS researchers must lead the charge in rearchitecting systems to push the boundaries of low latency datacenter communication. [sent-9, score-1.168]
10 5-10µs remote procedure calls are possible in the short term – two orders of magnitude better than today. [sent-10, score-0.511]
11 In the long term, moving the network interface on to the CPU core will make 1µs times feasible. [sent-11, score-0.194]
wordName wordTfidf (topN-words)
[('delays', 0.33), ('datacenter', 0.267), ('latency', 0.2), ('rumble', 0.176), ('rearchitect', 0.158), ('term', 0.155), ('ultra', 0.152), ('campus', 0.152), ('rearchitecting', 0.152), ('fungible', 0.148), ('bene', 0.148), ('interchangeable', 0.144), ('luiz', 0.144), ('barroso', 0.14), ('low', 0.137), ('ignored', 0.137), ('andre', 0.137), ('stephen', 0.137), ('crush', 0.129), ('ages', 0.125), ('propagation', 0.125), ('et', 0.124), ('distinguished', 0.124), ('articlesthe', 0.116), ('network', 0.114), ('boundaries', 0.11), ('burden', 0.109), ('researchers', 0.107), ('procedure', 0.107), ('ethernet', 0.105), ('argue', 0.103), ('turning', 0.101), ('warehouse', 0.099), ('sees', 0.097), ('implications', 0.094), ('era', 0.093), ('charge', 0.092), ('everywhere', 0.09), ('abstract', 0.086), ('orders', 0.085), ('sales', 0.084), ('possible', 0.083), ('instant', 0.082), ('explore', 0.082), ('magnitude', 0.081), ('times', 0.08), ('location', 0.076), ('effectively', 0.075), ('datacenters', 0.075), ('deployed', 0.075)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 1116 high scalability-2011-09-15-Paper: It's Time for Low Latency - Inventing the 1 Microsecond Datacenter
Introduction: In It's Time for Low Latency Stephen Rumble et al. explore the idea that it's time to rearchitect our stack to live in the modern era of low-latency datacenter instead of high-latency WANs. The implications for program architectures will be revolutionary . Luiz André Barroso , Distinguished Engineer at Google, sees ultra low latency as a way to make computer resources, to be as much as possible, fungible, that is they are interchangeable and location independent, effectively turning a datacenter into single computer. Abstract from the paper: The operating systems community has ignored network latency for too long. In the past, speed-of-light delays in wide area networks and unoptimized network hardware have made sub-100µs round-trip times impossible. However, in the next few years datacenters will be deployed with low-latency Ethernet. Without the burden of propagation delays in the datacenter campus and network delays in the Ethernet devices, it will be up to us to finish
2 0.29581419 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant
Introduction: The world has changed. And some things that should not have been forgotten, were lost. I found these words from the Lord of the Rings echoing in my head as I listened to a fascinating presentation by Luiz André Barroso , Distinguished Engineer at Google, concerning Google's legendary past, golden present, and apocryphal future. His talk, Warehouse-Scale Computing: Entering the Teenage Decade , was given at the Federated Computing Research Conference . Luiz clearly knows his stuff and was early at Google, so he has a deep and penetrating perspective on the technology. There's much to learn from, think about, and build. Lord of the Rings applies at two levels. At the change level, Middle Earth went through three ages . While listening to Luiz talk, it seems so has Google: Batch (indexes calculated every month), Warehouse (the datacenter is the computer), and Instant (make it all real-time). At the "what was forgot" level, in the Instant Age section of the talk, a common theme was
3 0.21746755 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
Introduction: Likewise the current belief that, in the case of artificial machines the very large and the very small are equally feasible and lasting is a manifest error. Thus, for example, a small obelisk or column or other solid figure can certainly be laid down or set up without danger of breaking, while the large ones will go to pieces under the slightest provocation, and that purely on account of their own weight. -- Galileo Galileo observed how things broke if they were naively scaled up. Interestingly, Google noticed a similar pattern when building larger software systems using the same techniques used to build smaller systems. Luiz André Barroso , Distinguished Engineer at Google, talks about this fundamental property of scaling systems in his fascinating talk, Warehouse-Scale Computing: Entering the Teenage Decade . Google found the larger the scale the greater the impact of latency variability. When a request is implemented by work done in parallel, as is common with today's service
4 0.17229915 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
Introduction: Update 8 : The Cost of Latency by James Hamilton. James summarizing some latency info from Steve Souder , Greg Linden , and Marissa Mayer . Speed [is] an undervalued and under-discussed asset on the web. Update 7: How do you know when you need more memcache servers? . Dathan Pattishall talks about using memcache not to scale, but to reduce latency and reduce I/O spikes, and how to use stats to know when more servers are needed. Update 6: Stock Traders Find Speed Pays, in Milliseconds . Goldman Sachs is making record profits off a 500 millisecond trading advantage. Yes, latency matters. As an interesting aside, Libet found 500 msecs is about the time it takes the brain to weave together an experience of consciousness from all our sensor inputs. Update 5: Shopzilla's Site Redo - You Get What You Measure . At the Velocity conference Phil Dixon, from Shopzilla, presented data showing a 5 second speed up resulted in a 25% increase in page views, a 10% increas
5 0.16124822 687 high scalability-2009-08-24-How Google Serves Data from Multiple Datacenters
Introduction: Update: Streamy Explains CAP and HBase's Approach to CAP . We plan to employ inter-cluster replication, with each cluster located in a single DC. Remote replication will introduce some eventual consistency into the system, but each cluster will continue to be strongly consistent. Ryan Barrett, Google App Engine datastore lead, gave this talk Transactions Across Datacenters (and Other Weekend Projects) at the Google I/O 2009 conference. While the talk doesn't necessarily break new technical ground, Ryan does an excellent job explaining and evaluating the different options you have when architecting a system to work across multiple datacenters. This is called multihoming , operating from multiple datacenters simultaneously. As multihoming is one of the most challenging tasks in all computing, Ryan's clear and thoughtful style comfortably leads you through the various options. On the trip you learn: The different multi-homing options are: Backups, Master-Slave, Multi-M
6 0.15613481 1316 high scalability-2012-09-04-Changing Architectures: New Datacenter Networks Will Set Your Code and Data Free
7 0.15256375 879 high scalability-2010-08-12-Think of Latency as a Pseudo-permanent Network Partition
8 0.14283553 1177 high scalability-2012-01-19-Is it time to get rid of the Linux OS model in the cloud?
9 0.12752306 1558 high scalability-2013-12-04-How Can Batching Requests Actually Reduce Latency?
10 0.12513877 1392 high scalability-2013-01-23-Building Redundant Datacenter Networks is Not For Sissies - Use an Outside WAN Backbone
11 0.11870165 839 high scalability-2010-06-09-Paper: Propagation Networks: A Flexible and Expressive Substrate for Computation
12 0.11315156 284 high scalability-2008-03-19-RAD Lab is Creating a Datacenter Operating System
13 0.10456354 768 high scalability-2010-02-01-What Will Kill the Cloud?
16 0.10296211 750 high scalability-2009-12-16-Building Super Scalable Systems: Blade Runner Meets Autonomic Computing in the Ambient Cloud
17 0.10189383 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
18 0.098256156 1039 high scalability-2011-05-12-Paper: Mind the Gap: Reconnecting Architecture and OS Research
19 0.095527865 1266 high scalability-2012-06-18-Google on Latency Tolerant Systems: Making a Predictable Whole Out of Unpredictable Parts
20 0.092124388 1310 high scalability-2012-08-23-Economies of Scale in the Datacenter: Gmail is 100x Cheaper to Run than Your Own Server
topicId topicWeight
[(0, 0.124), (1, 0.056), (2, 0.007), (3, 0.092), (4, -0.056), (5, -0.026), (6, 0.039), (7, 0.085), (8, -0.093), (9, -0.004), (10, -0.003), (11, -0.041), (12, -0.031), (13, 0.02), (14, 0.048), (15, 0.07), (16, -0.028), (17, 0.004), (18, 0.007), (19, -0.055), (20, 0.073), (21, 0.106), (22, -0.028), (23, -0.046), (24, -0.011), (25, 0.082), (26, -0.065), (27, -0.028), (28, -0.066), (29, -0.075), (30, 0.011), (31, -0.029), (32, -0.013), (33, 0.007), (34, 0.037), (35, 0.056), (36, -0.008), (37, -0.016), (38, -0.062), (39, 0.06), (40, 0.056), (41, 0.05), (42, -0.027), (43, -0.05), (44, -0.002), (45, -0.056), (46, -0.017), (47, -0.073), (48, 0.022), (49, -0.019)]
simIndex simValue blogId blogTitle
same-blog 1 0.987113 1116 high scalability-2011-09-15-Paper: It's Time for Low Latency - Inventing the 1 Microsecond Datacenter
Introduction: In It's Time for Low Latency Stephen Rumble et al. explore the idea that it's time to rearchitect our stack to live in the modern era of low-latency datacenter instead of high-latency WANs. The implications for program architectures will be revolutionary . Luiz André Barroso , Distinguished Engineer at Google, sees ultra low latency as a way to make computer resources, to be as much as possible, fungible, that is they are interchangeable and location independent, effectively turning a datacenter into single computer. Abstract from the paper: The operating systems community has ignored network latency for too long. In the past, speed-of-light delays in wide area networks and unoptimized network hardware have made sub-100µs round-trip times impossible. However, in the next few years datacenters will be deployed with low-latency Ethernet. Without the burden of propagation delays in the datacenter campus and network delays in the Ethernet devices, it will be up to us to finish
2 0.73580337 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
Introduction: Likewise the current belief that, in the case of artificial machines the very large and the very small are equally feasible and lasting is a manifest error. Thus, for example, a small obelisk or column or other solid figure can certainly be laid down or set up without danger of breaking, while the large ones will go to pieces under the slightest provocation, and that purely on account of their own weight. -- Galileo Galileo observed how things broke if they were naively scaled up. Interestingly, Google noticed a similar pattern when building larger software systems using the same techniques used to build smaller systems. Luiz André Barroso , Distinguished Engineer at Google, talks about this fundamental property of scaling systems in his fascinating talk, Warehouse-Scale Computing: Entering the Teenage Decade . Google found the larger the scale the greater the impact of latency variability. When a request is implemented by work done in parallel, as is common with today's service
3 0.71145552 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant
Introduction: The world has changed. And some things that should not have been forgotten, were lost. I found these words from the Lord of the Rings echoing in my head as I listened to a fascinating presentation by Luiz André Barroso , Distinguished Engineer at Google, concerning Google's legendary past, golden present, and apocryphal future. His talk, Warehouse-Scale Computing: Entering the Teenage Decade , was given at the Federated Computing Research Conference . Luiz clearly knows his stuff and was early at Google, so he has a deep and penetrating perspective on the technology. There's much to learn from, think about, and build. Lord of the Rings applies at two levels. At the change level, Middle Earth went through three ages . While listening to Luiz talk, it seems so has Google: Batch (indexes calculated every month), Warehouse (the datacenter is the computer), and Instant (make it all real-time). At the "what was forgot" level, in the Instant Age section of the talk, a common theme was
4 0.68835628 1558 high scalability-2013-12-04-How Can Batching Requests Actually Reduce Latency?
Introduction: Jeremy Edberg gave a talk on Scaling Reddit from 1 Million to 1 Billion–Pitfalls and Lessons and one of the issues they had was that they: Did not account for increased latency after moving to EC2. In the datacenter they had submillisecond access between machines so it was possible to make a 1000 calls to memache for one page load. Not so on EC2. Memcache access times increased 10x to a millisecond which made their old approach unusable. Fix was to batch calls to memcache so a large number of gets are in one request. Dave Pacheco had an interesting question about batching requests and its impact on latency: I was confused about the memcached problem after moving to the cloud. I understand why network latency may have gone from submillisecond to milliseconds, but how could you improve latency by batching requests? Shouldn't that improve efficiency, not latency, at the possible expense of latency (since some requests will wait on the client as they get batched)?
5 0.68126267 879 high scalability-2010-08-12-Think of Latency as a Pseudo-permanent Network Partition
Introduction: The title of this post is a quote from Ilya Grigorik's post Weak Consistency and CAP Implications . Besides the article being excellent, I thought this idea had something to add to the great NoSQL versus RDBMS debate, where Mike Stonebraker makes the argument that network partitions are rare so designing eventually consistent systems for such rare occurrence is not worth losing ACID semantics over. Even if network partitions are rare, latency between datacenters is not rare, so the game is still on. The rare-partition argument seems to flow from a centralized-distributed view of systems. Such systems are scale-out in that they grow by adding distributed nodes, but the nodes generally do not cross datacenter boundaries. The assumption is the network is fast enough that distributed operations are roughly homogenous between nodes. In a fully-distributed system the nodes can be dispersed across datacenters, which gives operations a widely variable performance profile. Because everyt
6 0.64796567 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
8 0.62722814 1213 high scalability-2012-03-22-Paper: Revisiting Network I-O APIs: The netmap Framework
9 0.62657571 1316 high scalability-2012-09-04-Changing Architectures: New Datacenter Networks Will Set Your Code and Data Free
11 0.62012672 1392 high scalability-2013-01-23-Building Redundant Datacenter Networks is Not For Sissies - Use an Outside WAN Backbone
12 0.60821635 1266 high scalability-2012-06-18-Google on Latency Tolerant Systems: Making a Predictable Whole Out of Unpredictable Parts
13 0.60467678 284 high scalability-2008-03-19-RAD Lab is Creating a Datacenter Operating System
14 0.59958988 645 high scalability-2009-06-30-Hot New Trend: Linking Clouds Through Cheap IP VPNs Instead of Private Lines
15 0.59777558 1594 high scalability-2014-02-12-Paper: Network Stack Specialization for Performance
16 0.59600794 1651 high scalability-2014-05-20-It's Networking. In Space! Or How E.T. Will Phone Home.
17 0.58462948 1177 high scalability-2012-01-19-Is it time to get rid of the Linux OS model in the cloud?
18 0.57381964 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)
19 0.57003093 409 high scalability-2008-10-13-Challenges from large scale computing at Google
20 0.56666541 687 high scalability-2009-08-24-How Google Serves Data from Multiple Datacenters
topicId topicWeight
[(1, 0.076), (2, 0.194), (40, 0.01), (61, 0.02), (77, 0.426), (79, 0.106), (94, 0.071)]
simIndex simValue blogId blogTitle
Introduction: Successful software design is all about trade-offs. In the typical (if there is such a thing) distributed system, recognizing the importance of trade-offs within the design of your architecture is integral to the success of your system. Despite this reality, I see time and time again, developers choosing a particular solution based on an ill-placed belief in their solution as a “silver bullet”, or a solution that conquers all, despite the inevitable occurrence of changing requirements. Regardless of the reasons behind this phenomenon, I’d like to outline a few of the methods I use to ensure that I’m making good scalable decisions without losing sight of the trade-offs that accompany them. I’d also like to compile (pun intended) the issues at hand, by formulating a simple theorem that we can use to describe this oft occurring situation.
same-blog 2 0.8834818 1116 high scalability-2011-09-15-Paper: It's Time for Low Latency - Inventing the 1 Microsecond Datacenter
Introduction: In It's Time for Low Latency Stephen Rumble et al. explore the idea that it's time to rearchitect our stack to live in the modern era of low-latency datacenter instead of high-latency WANs. The implications for program architectures will be revolutionary . Luiz André Barroso , Distinguished Engineer at Google, sees ultra low latency as a way to make computer resources, to be as much as possible, fungible, that is they are interchangeable and location independent, effectively turning a datacenter into single computer. Abstract from the paper: The operating systems community has ignored network latency for too long. In the past, speed-of-light delays in wide area networks and unoptimized network hardware have made sub-100µs round-trip times impossible. However, in the next few years datacenters will be deployed with low-latency Ethernet. Without the burden of propagation delays in the datacenter campus and network delays in the Ethernet devices, it will be up to us to finish
Introduction: James Hamilton in Counting Servers is Hard has an awesome breakdown of what one million plus servers really means in terms of resource usage. The summary from his calculations are eye popping: Facilities: 15 to 30 large datacenters Capital expense: $4.25 Billion Total power: 300MW Power Consumption: 2.6TWh annually The power consumption is about the same as used by Nicaragua and the capital cost is about a third of what Americans spent on video games in 2012. Now that's web scale.
4 0.85128319 258 high scalability-2008-02-24-Yandex Architecture
Introduction: Update: Anatomy of a crash in a new part of Yandex written in Django . Writing to a magic session variable caused an unexpected write into an InnoDB database on every request. Writes took 6-7 seconds because of index rebuilding. Lots of useful details on the sizing of their system, what went wrong, and how they fixed it. Yandex is a Russian search engine with 3.5 billion pages in their search index. We only know a few fun facts about how they do things, nothing at a detailed architecture level. Hopefully we'll learn more later, but I thought it would still be interesting. From Allen Stern's interview with Yandex's CTO Ilya Segalovich, we learn: 3.5 billion pages in the search index. Over several thousand servers. 35 million searches a day. Several data centers around Russia. Two-layer architecture. The database is split in pieces and when a search is requested, it pulls the bits from the different database servers and brings it together for the user. Languages
5 0.83034772 766 high scalability-2010-01-26-Product: HyperGraphDB - A Graph Database
Introduction: With the success of Neo4j as a graph database in the NoSQL revolution, it's interesting to see another graph database, HyperGraphDB , in the mix. Their quick blurb on HyperGraphDB says it is a: general purpose, extensible, portable, distributed, embeddable, open-source data storage mechanism. It is a graph database designed specifically for artificial intelligence and semantic web projects, it can also be used as an embedded object-oriented database for projects of all sizes. From the NoSQL Archive the summary on HyperGraphDB is: API: Java (and Java Langs), Written in: Java , Query Method: Java or P2P, Replication: P2P , Concurrency: STM , Misc: Open-Source, Especially for AI and Semantic Web. So it has some interesting features, like software transactional memory and P2P for data distribution , but I found that my first and most obvious question was not answered: what the heck is a hypergraph and why do I care? Buried in the tutorial was: A HyperGraphD
6 0.82622403 1195 high scalability-2012-02-17-Stuff The Internet Says On Scalability For February 17, 2012
7 0.81709743 211 high scalability-2008-01-13-Google Reveals New MapReduce Stats
8 0.80678213 525 high scalability-2009-03-05-Product: Amazon Simple Storage Service
9 0.79820073 959 high scalability-2010-12-17-Stuff the Internet Says on Scalability For December 17th, 2010
10 0.79509461 753 high scalability-2009-12-21-Hot Holiday Scalability Links for 2009
11 0.77542031 1531 high scalability-2013-10-13-AIDA: Badoo’s journey into Continuous Integration
12 0.74854243 439 high scalability-2008-11-10-Scalability Perspectives #1: Nicholas Carr – The Big Switch
13 0.73896021 1059 high scalability-2011-06-14-A TripAdvisor Short
14 0.73431361 1377 high scalability-2012-12-26-Ask HS: What will programming and architecture look like in 2020?
15 0.72034848 1158 high scalability-2011-12-16-Stuff The Internet Says On Scalability For December 16, 2011
16 0.69848698 612 high scalability-2009-05-31-Parallel Programming for real-world
17 0.6920886 1188 high scalability-2012-02-06-The Design of 99designs - A Clean Tens of Millions Pageviews Architecture
18 0.67937613 1571 high scalability-2014-01-02-xkcd: How Standards Proliferate:
20 0.66964507 1567 high scalability-2013-12-20-Stuff The Internet Says On Scalability For December 20th, 2013