high_scalability high_scalability-2014 high_scalability-2014-1646 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: This is a guest repost by Venkatesh CM at Architecture Issues Scaling Web Applications . I will cover architecture issues that show up while scaling and performance tuning large scale web application in this blog. Lets start by defining few terms to create common understanding and vocabulary. Later on I will go through different issues that pop-up while scaling web application like Architecture bottlenecks Scaling Database CPU Bound Application IO Bound Application Determining optimal thread pool size of an web application will be covered in next blog. Performance Term performance of web application is used to mean several things. Most developers are primarily concerned with are response time and scalability. Response Time Is the time taken by web application to process request and return response. Applications should respond to requests (response time) within acceptable duration. If application is taking beyond the acceptable time, it is said to
sentIndex sentText sentNum sentScore
1 I will cover architecture issues that show up while scaling and performance tuning large scale web application in this blog. [sent-2, score-0.525]
2 Later on I will go through different issues that pop-up while scaling web application like Architecture bottlenecks Scaling Database CPU Bound Application IO Bound Application Determining optimal thread pool size of an web application will be covered in next blog. [sent-4, score-0.866]
3 Response Time Is the time taken by web application to process request and return response. [sent-7, score-0.491]
4 If application is taking beyond the acceptable time, it is said to be non-performing or degraded. [sent-9, score-0.499]
5 Scalability The web application is said to be scalable if by adding more hardware, application can linearly take more requests than before. [sent-10, score-1.022]
6 Two ways of adding more hardware are Scaling Up (vertical scaling) :– increasing the number CPUs or adding faster CPUs on a single box. [sent-11, score-0.52]
7 But increasing the number of requests that an application can handle on a single commodity hardware box is also important. [sent-14, score-0.935]
8 An application is said to be performing well if it can handle more requests with-out degrading response time by just adding more resources. [sent-15, score-1.078]
9 application might have acceptable response times but can not handle more than certain number of requests or application is handle increasing number of requests but has poor or long response times. [sent-18, score-1.799]
10 Adding multiple Load balancers is rare as a single box running nginx or HAProxy can handle more than 20K concurrent connections per box compared to web application boxes which can handle few thousand concurrent requests. [sent-27, score-0.997]
11 So a single load balancer box can handle several web application boxes. [sent-28, score-0.673]
12 Master-Slave provides limited scaling of reads beyond which developers has to split the database into multiple databases. [sent-32, score-0.557]
13 Another way to split database is by moving few columns of an entity to one database and few other columns to another database. [sent-38, score-0.642]
14 Transiting from single database to multiple database using partitioning or sharding is a challenging task. [sent-42, score-0.565]
15 Architecture Bottlenecks Scaling bottlenecks are formed due to two issues Centralised component A component in application architecture which can not be scaled out adds an upper limit on number of requests that entire architecture or request pipeline can handle. [sent-43, score-1.076]
16 High latency component A slow component in request pipeline puts lower limit on the response time of the application. [sent-44, score-0.648]
17 CPU Bound Application An application is said to be CPU bound if application throughput is limited by its CPU. [sent-46, score-0.979]
18 By increasing CPU speed application response time can be reduced. [sent-47, score-0.671]
19 IO Bound Application An application is said to be IO bound if application throughput is limited by its IO or network operations and increasing CPU speed does not bring down application response times. [sent-55, score-1.582]
20 Most applications are IO bound due to the CRUD operation in most applications Performance tuning or scaling IO bound applications is a difficult job due to its dependency on other systems downstream. [sent-56, score-1.137]
wordName wordTfidf (topN-words)
[('bound', 0.276), ('application', 0.25), ('response', 0.205), ('eg', 0.181), ('io', 0.181), ('database', 0.165), ('applicationan', 0.149), ('bottlenecksscaling', 0.149), ('boundapplications', 0.149), ('operationsapplications', 0.149), ('increasing', 0.148), ('split', 0.144), ('box', 0.138), ('said', 0.13), ('requests', 0.12), ('acceptable', 0.119), ('handle', 0.117), ('applications', 0.112), ('component', 0.108), ('crud', 0.107), ('adding', 0.105), ('scenarios', 0.1), ('scaling', 0.099), ('scaled', 0.097), ('web', 0.091), ('customer', 0.09), ('hardware', 0.088), ('issues', 0.085), ('columns', 0.084), ('performing', 0.083), ('request', 0.082), ('partitioning', 0.081), ('sharding', 0.078), ('cpu', 0.078), ('pipeline', 0.077), ('load', 0.077), ('multiple', 0.076), ('linearly', 0.076), ('figuring', 0.076), ('due', 0.075), ('number', 0.074), ('limited', 0.073), ('splitting', 0.072), ('balancers', 0.07), ('shown', 0.069), ('time', 0.068), ('depended', 0.067), ('precomputing', 0.067), ('drown', 0.067), ('bycaching', 0.067)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
Introduction: This is a guest repost by Venkatesh CM at Architecture Issues Scaling Web Applications . I will cover architecture issues that show up while scaling and performance tuning large scale web application in this blog. Lets start by defining few terms to create common understanding and vocabulary. Later on I will go through different issues that pop-up while scaling web application like Architecture bottlenecks Scaling Database CPU Bound Application IO Bound Application Determining optimal thread pool size of an web application will be covered in next blog. Performance Term performance of web application is used to mean several things. Most developers are primarily concerned with are response time and scalability. Response Time Is the time taken by web application to process request and return response. Applications should respond to requests (response time) within acceptable duration. If application is taking beyond the acceptable time, it is said to
2 0.19831581 359 high scalability-2008-07-29-Ehcache - A Java Distributed Cache
Introduction: Ehcache is a pure Java cache with the following features: fast, simple, small foot print, minimal dependencies, provides memory and disk stores for scalability into gigabytes, scalable to hundreds of caches is a pluggable cache for Hibernate, tuned for high concurrent load on large multi-cpu servers, provides LRU, LFU and FIFO cache eviction policies, and is production tested. Ehcache is used by LinkedIn to cache member profiles. The user guide says it's possible to get at 2.5 times system speedup for persistent Object Relational Caching, a 1000 times system speedup for Web Page Caching, and a 1.6 times system speedup Web Page Fragment Caching. From the website: Introduction Ehcache is a cache library. Before getting into ehcache, it is worth stepping back and thinking about caching generally. About Caches Wiktionary defines a cache as A store of things that will be required in future, and can be retrieved rapidly . That is the nub of it. In computer science terms, a cac
3 0.16605395 18 high scalability-2007-07-16-Paper: MySQL Scale-Out by application partitioning
Introduction: MySQL Scale-Out by application partitioning by Oli Sennhauser Eventually every database system hit its limits. Especially on the Internet, where you have millions of users which theoretically access your database simultaneously, eventually your IO system will be a bottleneck. [A] promising but more complex solution with nearly no scale-out limits is application partitioning. If and when you get into the top-1000 rank on alexa [1], you have to think about such solutions. A Quick Hit of What's Inside Horizontal application partitioning, Vertical application partitioning, Disk IO calculations, How to partition an entity
4 0.16424634 313 high scalability-2008-05-02-Friends for Sale Architecture - A 300 Million Page View-Month Facebook RoR App
Introduction: Update: Jake in Does Django really scale better than Rails? thinks apps like FFS shouldn't need so much hardware to scale. In a short three months Friends for Sale (think Hot-or-Not with a market economy) grew to become a top 10 Facebook application handling 200 gorgeous requests per second and a stunning 300 million page views a month. They did all this using Ruby on Rails, two part time developers, a cluster of a dozen machines, and a fairly standard architecture. How did Friends for Sale scale to sell all those beautiful people? And how much do you think your friends are worth on the open market? Site: http://www.facebook.com/apps/application.php?id=7019261521 Information Sources Siqi Chen and Alexander Le, co-creators of Friends for Sale, answering my standard questionairre. Virality on Facebook The Platform Ruby on Rails CentOS 5 (64 bit) Capistrano - update and restart application servers. Memcached MySQL Nginx Starling - distrib
5 0.16070203 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
Introduction: Too often software design patterns are overlooked by network and application delivery network architects but these patterns are often equally applicable to addressing a broad range of architectural challenges in the application delivery tier of the data center. By Lori Mac Vittie, F5 Networks The “ High Scalability ” blog is fast becoming one of my favorite reads. Last week did not disappoint with a post highlighting a set of scalability design patterns that was, apparently, inspired by yet another High Scalability post on “ 6 Ways to Kill Your Servers: Learning to Scale the Hard Way. ” Credit:Michael Chow/azcentral.com This particular post caught my attention primarily because although I’ve touched on many of these patterns in the past, I’ve never thought to call them what they are: scalability patterns. That’s probably a side-effect of forgetting that building an architecture of any kind is at its core computer science and thus
6 0.15642025 602 high scalability-2009-05-17-Scaling Django Web Apps by Mike Malone
7 0.14784361 728 high scalability-2009-10-26-Facebook's Memcached Multiget Hole: More machines != More Capacity
8 0.14727396 538 high scalability-2009-03-16-Are Cloud Based Memory Architectures the Next Big Thing?
9 0.14597812 936 high scalability-2010-11-09-Facebook Uses Non-Stored Procedures to Update Social Graphs
10 0.14253861 821 high scalability-2010-05-03-MocoSpace Architecture - 3 Billion Mobile Page Views a Month
11 0.13919578 1331 high scalability-2012-10-02-An Epic TripAdvisor Update: Why Not Run on the Cloud? The Grand Experiment.
12 0.13906866 1038 high scalability-2011-05-11-Troubleshooting response time problems – why you cannot trust your system metrics
13 0.13681853 1413 high scalability-2013-02-27-42 Monster Problems that Attack as Loads Increase
14 0.13554657 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results
15 0.13304056 1654 high scalability-2014-06-05-Cloud Architecture Revolution
16 0.13217358 920 high scalability-2010-10-15-Troubles with Sharding - What can we learn from the Foursquare Incident?
17 0.13161299 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
18 0.13151875 96 high scalability-2007-09-18-Amazon Architecture
19 0.13062486 1591 high scalability-2014-02-05-Little’s Law, Scalability and Fault Tolerance: The OS is your bottleneck. What you can do?
20 0.12984356 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service
topicId topicWeight
[(0, 0.256), (1, 0.097), (2, -0.027), (3, -0.097), (4, -0.023), (5, 0.046), (6, 0.07), (7, -0.068), (8, -0.095), (9, -0.041), (10, -0.003), (11, 0.03), (12, -0.043), (13, 0.038), (14, -0.03), (15, -0.057), (16, 0.038), (17, 0.005), (18, 0.065), (19, 0.042), (20, 0.006), (21, 0.067), (22, 0.008), (23, -0.101), (24, 0.09), (25, -0.004), (26, -0.055), (27, -0.012), (28, 0.07), (29, 0.058), (30, 0.07), (31, -0.042), (32, 0.076), (33, 0.064), (34, 0.035), (35, -0.034), (36, -0.075), (37, -0.014), (38, -0.013), (39, -0.031), (40, -0.019), (41, -0.019), (42, -0.052), (43, -0.06), (44, 0.04), (45, 0.058), (46, 0.053), (47, 0.005), (48, -0.049), (49, -0.04)]
simIndex simValue blogId blogTitle
same-blog 1 0.97866976 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
Introduction: This is a guest repost by Venkatesh CM at Architecture Issues Scaling Web Applications . I will cover architecture issues that show up while scaling and performance tuning large scale web application in this blog. Lets start by defining few terms to create common understanding and vocabulary. Later on I will go through different issues that pop-up while scaling web application like Architecture bottlenecks Scaling Database CPU Bound Application IO Bound Application Determining optimal thread pool size of an web application will be covered in next blog. Performance Term performance of web application is used to mean several things. Most developers are primarily concerned with are response time and scalability. Response Time Is the time taken by web application to process request and return response. Applications should respond to requests (response time) within acceptable duration. If application is taking beyond the acceptable time, it is said to
2 0.80141002 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
Introduction: Too often software design patterns are overlooked by network and application delivery network architects but these patterns are often equally applicable to addressing a broad range of architectural challenges in the application delivery tier of the data center. By Lori Mac Vittie, F5 Networks The “ High Scalability ” blog is fast becoming one of my favorite reads. Last week did not disappoint with a post highlighting a set of scalability design patterns that was, apparently, inspired by yet another High Scalability post on “ 6 Ways to Kill Your Servers: Learning to Scale the Hard Way. ” Credit:Michael Chow/azcentral.com This particular post caught my attention primarily because although I’ve touched on many of these patterns in the past, I’ve never thought to call them what they are: scalability patterns. That’s probably a side-effect of forgetting that building an architecture of any kind is at its core computer science and thus
3 0.76712805 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
Introduction: We've referenced this 189 slide masterpiece by Ask Bjorn Hansen before, but it was hidden without its own first class link. He describes his presentation as 3 hours of 5 minute lightening talks and that sounds about right. The presentation covers: overall platform and architecture considerations involved in tuning applications from a holistic perspective. You’ll be shown design scalable architectures for dynamic, high-volume web sites. Topics covered include caching, scalable database design, replication architecture, load-balancing, and architectural decisions derived from many years of experience. His prime directive of scaling: Think Horizontally at every point in your architecture, not just at the web tier. You may not agree with everything, but there's a lot of useful advice. Here's a summary of some of what is covered: Benchmarking Vertical scaling sucks. Horizontal scaling rocks. Run many application servers Don't keep state in the app server Be sta
4 0.74788481 381 high scalability-2008-09-08-Guerrilla Capacity Planning and the Law of Universal Scalability
Introduction: In the era of Web 2.0 traditional approaches to capacity planning are often difficult to implement. Guerrilla Capacity Planning facilitates rapid forecasting of capacity requirements based on the opportunistic use of whatever performance data and tools are available. One unique Guerrilla tool is Virtual Load Testing, based on Dr. Gunther's "Universal Law of Computational Scaling", which provides a highly cost-effective method for assessing application scalability. Neil Gunther, M.Sc., Ph.D. is an internationally recognized computer system performance consultant who founded Performance Dynamics Company in 1994. Some reasons why you should understand this law: 1. A lot of people use the term "scalability" without clearly defining it, let alone defining it quantitatively. Computer system scalability must be quantified. If you can't quantify it, you can't guarantee it. The universal law of computational scaling provides that quantification. 2. One the greatest impediments to applying
5 0.73582828 1325 high scalability-2012-09-19-The 4 Building Blocks of Architecting Systems for Scale
Introduction: If you are looking for an excellent overview of general architecture principles then take a look at Will Larson's Introduction to Architecting Systems for Scale . Based on his experiences at Yahoo! and Digg, Will covers key concepts in some depth. A quick gloss on the building blocks: Load Balancing: Scalability & Redundancy . Horizontal scalability and redundancy are usually achieved via load balancing, the spreading of requests across multiple resources. Smart Clients . The client has a list of hosts and load balances across that list of hosts. Upside is simple for programmers. Downside is it's hard to update and change. Hardware Load Balancers . Targeted at larger companies, this is dedicated load balancing hardware. Upside is performance. Downside is cost and complexity. Software Load Balancers . The recommended approach, it's software that handles load balancing, health checks, etc. Caching . Make better use of resources you already have. Pr
6 0.73211575 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
7 0.72871542 18 high scalability-2007-07-16-Paper: MySQL Scale-Out by application partitioning
8 0.71390206 936 high scalability-2010-11-09-Facebook Uses Non-Stored Procedures to Update Social Graphs
9 0.70923048 391 high scalability-2008-09-23-The 7 Stages of Scaling Web Apps
10 0.70849276 602 high scalability-2009-05-17-Scaling Django Web Apps by Mike Malone
11 0.70726621 877 high scalability-2010-08-12-Designing Web Applications for Scalability
12 0.70439631 389 high scalability-2008-09-23-How to Scale with Ruby on Rails
14 0.69918591 1082 high scalability-2011-07-18-New Relic Architecture - Collecting 20+ Billion Metrics a Day
15 0.69703925 1565 high scalability-2013-12-16-22 Recommendations for Building Effective High Traffic Web Software
16 0.69470173 679 high scalability-2009-08-11-13 Scalability Best Practices
17 0.6929552 372 high scalability-2008-08-27-Updating distributed web applications
18 0.69104838 1038 high scalability-2011-05-11-Troubleshooting response time problems – why you cannot trust your system metrics
19 0.68618262 250 high scalability-2008-02-17-Web Accelerators - snake oil or miracle remedy?
20 0.68454915 924 high scalability-2010-10-21-What is Network-based Application Virtualization and Why Do You Need It?
topicId topicWeight
[(1, 0.157), (2, 0.286), (10, 0.048), (30, 0.02), (49, 0.113), (51, 0.023), (61, 0.086), (77, 0.034), (79, 0.072), (85, 0.028), (94, 0.054)]
simIndex simValue blogId blogTitle
1 0.97165722 1311 high scalability-2012-08-24-Stuff The Internet Says On Scalability For August 24, 2012
Introduction: It's HighScalability Time: 500 TB/day: Facebook data Quotable Quotes: Tumblr mobocracy : This is what migrating a billion cache objects into a new cache pool looks like #hoti it is possible to build all to all wdm networks where there is a wavelength per core. A Generation Lost in the Bazaar . The problem is Cathedrals are multi-generation projects, built by master craftsman, using an empirical process, not engineering principles. There is no complete specification, it's iterative and adaptive. How Bazaar. Here's a unique look at how the new Digg 4 structured their architecture and development processes to scale down to 14 engineers from a high of 40 engineers for the old Digg. As the team shrunk very few new unit tests were written and the system tests were dumped. Using Thrift between components helped coordinate the team. A dark rollout mechanism allowed them to rollout and test features on a subset of users. Development team used
2 0.96664113 400 high scalability-2008-10-01-The Pattern Bible for Distributed Computing
Introduction: Software design patterns are an emerging tool for guiding and documenting system design. Patterns usually describe software abstractions used by advanced designers and programmers in their software. Patterns can provide guidance for designing highly scalable distributed systems. Let's see how! Patterns are in essence solutions to problems. Most of them are expressed in a format called Alexandrian form which draws on constructs used by Christopher Alexander. There are variants but most look like this: The pattern name The problem the pattern is trying to solve Context Solution Examples Design rationale: This tells where the pattern came from, why it works, and why experts use it Patterns rarely stand alone. Each pattern works on a context, and transforms the system in that context to produce a new system in a new context. New problems arise in the new system and context, and the next ‘‘layer’’ of patterns can be applied. A pattern language is a structured col
same-blog 3 0.96516919 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
Introduction: This is a guest repost by Venkatesh CM at Architecture Issues Scaling Web Applications . I will cover architecture issues that show up while scaling and performance tuning large scale web application in this blog. Lets start by defining few terms to create common understanding and vocabulary. Later on I will go through different issues that pop-up while scaling web application like Architecture bottlenecks Scaling Database CPU Bound Application IO Bound Application Determining optimal thread pool size of an web application will be covered in next blog. Performance Term performance of web application is used to mean several things. Most developers are primarily concerned with are response time and scalability. Response Time Is the time taken by web application to process request and return response. Applications should respond to requests (response time) within acceptable duration. If application is taking beyond the acceptable time, it is said to
4 0.96313703 1114 high scalability-2011-09-13-Must see: 5 Steps to Scaling MongoDB (Or Any DB) in 8 Minutes
Introduction: Jared Rosoff concisely, effectively, entertainingly, and convincingly gives an 8 minute MongoDB tutorial on scaling MongoDB at Scale Out Camp . The ideas aren't just limited to MongoDB, they work for most any database: Optimize your queries; Know your working set size; Tune your file system; Choose the right disks; Shard. Here's an explanation of all 5 strategies: Optimize your queries . Computer science works. Complexity analysis works. A btree search is faster than a table scan. So analyze your queries. Use explain to see what your query is doing. If it is saying it's using a cursor then it's doing a table scan. That's slow. Look at the number of documents it looks at to satisfy a query. Look at how long it takes. Fix: add indexes. It doesn't matter if you are running on 1 or 100 servers. Know your working set size . Sticking memcache in front of your database is silly. You have lots of RAM, use it. Embed your cache in the database, which is how MongoDB works. Working set
5 0.95515519 1359 high scalability-2012-11-15-Gone Fishin': Justin.Tv's Live Video Broadcasting Architecture
Introduction: This is one of my favorite posts for a couple of reasons. I think it gives a lot of useful information in an interesting space. And Kyle Vogt was just a real pleasure to talk to. He was very helpful and forthcoming, which makes the whole experience better for everyone. The future is live. The future is real-time. The future is now. That's the hype anyway. And as it has a habit of doing, the hype is slowly becoming reality. We are seeing live searches, live tweets, live location, live reality augmentation, live crab (fresh and local), and live event publishing. One of the most challenging of all live technologies is that of live video broadcasting. Imagine a world in which everyone becomes a broadcaster and a consumer of video streams, all in real-time (< 250 msec latency), all so you can talk and interact directly without feeling like you are in the middle of a time shift war. The resources and the engineering needed to make this happened must be substantial. How do you do tha
6 0.95496392 796 high scalability-2010-03-16-Justin.tv's Live Video Broadcasting Architecture
7 0.95004302 183 high scalability-2007-12-12-Report from OpenSocial Meetup at Google
8 0.9470492 823 high scalability-2010-05-05-How will memristors change everything?
9 0.94439977 568 high scalability-2009-04-14-Designing a Scalable Twitter
10 0.94402176 1407 high scalability-2013-02-15-Stuff The Internet Says On Scalability For February 15, 2013
11 0.94365788 1129 high scalability-2011-09-30-Stuff The Internet Says On Scalability For September 30, 2011
12 0.94364625 1638 high scalability-2014-04-28-How Disqus Went Realtime with 165K Messages Per Second and Less than .2 Seconds Latency
13 0.94283271 356 high scalability-2008-07-22-Scaling Bumper Sticker: A 1 Billion Page Per Month Facebook RoR App
14 0.94246829 1269 high scalability-2012-06-20-iDoneThis - Scaling an Email-based App from Scratch
15 0.94239879 1501 high scalability-2013-08-13-In Memoriam: Lavabit Architecture - Creating a Scalable Email Service
16 0.94203067 821 high scalability-2010-05-03-MocoSpace Architecture - 3 Billion Mobile Page Views a Month
17 0.94188398 1258 high scalability-2012-06-05-Thesis: Concurrent Programming for Scalable Web Architectures
18 0.94161618 1602 high scalability-2014-02-26-The WhatsApp Architecture Facebook Bought For $19 Billion
19 0.94149339 1339 high scalability-2012-10-12-Stuff The Internet Says On Scalability For October 12, 2012
20 0.94086438 884 high scalability-2010-08-23-6 Ways to Kill Your Servers - Learning How to Scale the Hard Way