high_scalability high_scalability-2009 high_scalability-2009-684 knowledge-graph by maker-knowledge-mining
Source: html
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
sentIndex sentText sentNum sentScore
1 We've referenced this 189 slide masterpiece by Ask Bjorn Hansen before, but it was hidden without its own first class link. [sent-1, score-0.324]
2 He describes his presentation as 3 hours of 5 minute lightening talks and that sounds about right. [sent-2, score-0.29]
3 The presentation covers: overall platform and architecture considerations involved in tuning applications from a holistic perspective. [sent-3, score-0.703]
4 You’ll be shown design scalable architectures for dynamic, high-volume web sites. [sent-4, score-0.084]
5 Topics covered include caching, scalable database design, replication architecture, load-balancing, and architectural decisions derived from many years of experience. [sent-5, score-0.314]
6 His prime directive of scaling: Think Horizontally at every point in your architecture, not just at the web tier. [sent-6, score-0.256]
7 You may not agree with everything, but there's a lot of useful advice. [sent-7, score-0.187]
8 Here's a summary of some of what is covered: Benchmarking Vertical scaling sucks. [sent-8, score-0.288]
9 Run many application servers Don't keep state in the app server Be stateless Optimization is necessary, but is different than scalability. [sent-10, score-0.084]
10 Master-master setup facilitates on-line schema changes. [sent-23, score-0.123]
11 Create summary tables and summary databases rather than do COUNT and GROUP-BY at runtime. [sent-24, score-0.396]
12 If it fails you should just be able to run it again. [sent-26, score-0.083]
13 Enable query logging and take a look at what your app is doing. [sent-32, score-0.305]
14 Load balancing is the key to horizontal scaling. [sent-47, score-0.11]
15 This is just a high level blitz through the presentation. [sent-65, score-0.165]
16 Topics are given a lot more detail in the presentation. [sent-66, score-0.099]
17 Audio of Ask's dulcet tones would be nice, but there's still a lot to learn here. [sent-67, score-0.099]
wordName wordTfidf (topN-words)
[('tuning', 0.228), ('covered', 0.208), ('summary', 0.198), ('bjorn', 0.165), ('blitz', 0.165), ('light', 0.156), ('lightening', 0.155), ('topics', 0.146), ('directive', 0.142), ('query', 0.141), ('yslow', 0.138), ('presentation', 0.135), ('referenced', 0.134), ('apis', 0.132), ('holistic', 0.131), ('ask', 0.13), ('flushed', 0.128), ('considerations', 0.125), ('facilitates', 0.123), ('incur', 0.123), ('vs', 0.121), ('audio', 0.114), ('prime', 0.114), ('invalidation', 0.112), ('balancing', 0.11), ('slide', 0.107), ('derived', 0.106), ('swap', 0.105), ('loosely', 0.103), ('skip', 0.101), ('lot', 0.099), ('procedures', 0.098), ('memory', 0.096), ('coupled', 0.095), ('partial', 0.092), ('slides', 0.091), ('scaling', 0.09), ('agree', 0.088), ('deployments', 0.088), ('queuing', 0.085), ('architecture', 0.084), ('shown', 0.084), ('app', 0.084), ('covers', 0.084), ('clean', 0.083), ('fails', 0.083), ('hidden', 0.083), ('count', 0.081), ('logging', 0.08), ('assume', 0.079)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 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
2 0.13925143 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
3 0.12875497 360 high scalability-2008-08-04-A Bunch of Great Strategies for Using Memcached and MySQL Better Together
Introduction: The primero recommendation for speeding up a website is almost always to add cache and more cache. And after that add a little more cache just in case. Memcached is almost always given as the recommended cache to use. What we don't often hear is how to effectively use a cache in our own products. MySQL hosted two excellent webinars (referenced below) on the subject of how to deploy and use memcached. The star of the show, other than MySQL of course, is Farhan Mashraqi of Fotolog. You may recall we did an earlier article on Fotolog in Secrets to Fotolog's Scaling Success , which was one of my personal favorites. Fotolog, as they themselves point out, is probably the largest site nobody has ever heard of, pulling in more page views than even Flickr. Fotolog has 51 instances of memcached on 21 servers with 175G in use and 254G available. As a large successful photo-blogging site they have very demanding performance and scaling requirements. To meet those requirements they've developed a
4 0.11990006 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
5 0.11174858 948 high scalability-2010-11-24-Great Introductory Video on Scalability from Harvard Computer Science
Introduction: Professor David Malan gives a very good lecture on scalability for dynamic websites. It's not highly technical, it's an extension course, but it's a great introduction to a wide variety of topics. I really like his teaching style. He continually asks questions, prompts for input, and gives accessible explanations. Some of the topics covered: vertical scaling; horizontal scaling; PHP acceleration; load balancing: DNS, L7, sticky sessions, load balancers; caching; MySQL: replication, load balancing, partitioning, high availability. Watch it on Academic Earth This is one lecture in a series of 13 lectures on building dynamic websites. Students learn how to: build dynamic websites with Ajax and with Linux , Apache , MySQL , and PHP ( LAMP ); set up domain names with DNS ; structure pages with XHTML and CSS how to program in JavaScript and PHP ; configure Apache and MySQL ; design and query databases with SQL ; use Ajax with both XML and JSON ;
6 0.1083039 954 high scalability-2010-12-06-What the heck are you actually using NoSQL for?
7 0.10761721 1240 high scalability-2012-05-07-Startups are Creating a New System of the World for IT
8 0.10619307 15 high scalability-2007-07-16-Blog: MySQL Performance Blog - Everything about MySQL Performance.
9 0.10584915 1032 high scalability-2011-05-02-Stack Overflow Makes Slow Pages 100x Faster by Simple SQL Tuning
10 0.10526571 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
11 0.10464571 602 high scalability-2009-05-17-Scaling Django Web Apps by Mike Malone
12 0.10271377 517 high scalability-2009-02-21-Google AppEngine - A Second Look
13 0.10216912 427 high scalability-2008-10-22-Server load balancing architectures, Part 2: Application-level load balancing
14 0.10034811 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
15 0.10030489 224 high scalability-2008-01-27-Scalability vs Performance vs Availability vs Reliability.. Also scale up vs scale out ???
16 0.10028107 1064 high scalability-2011-06-20-35+ Use Cases for Choosing Your Next NoSQL Database
17 0.10024629 674 high scalability-2009-08-07-The Canonical Cloud Architecture
18 0.099476151 1199 high scalability-2012-02-27-Zen and the Art of Scaling - A Koan and Epigram Approach
19 0.099348724 6 high scalability-2007-07-11-Friendster Architecture
20 0.099061333 906 high scalability-2010-09-22-Applying Scalability Patterns to Infrastructure Architecture
topicId topicWeight
[(0, 0.207), (1, 0.103), (2, -0.025), (3, -0.037), (4, 0.028), (5, 0.056), (6, -0.033), (7, -0.045), (8, -0.045), (9, 0.007), (10, -0.013), (11, -0.017), (12, -0.006), (13, 0.031), (14, -0.072), (15, -0.055), (16, 0.014), (17, -0.003), (18, 0.068), (19, 0.026), (20, -0.0), (21, -0.001), (22, -0.017), (23, -0.009), (24, 0.028), (25, 0.005), (26, 0.006), (27, 0.023), (28, 0.032), (29, 0.029), (30, -0.008), (31, -0.051), (32, 0.036), (33, -0.006), (34, 0.001), (35, -0.0), (36, -0.063), (37, -0.021), (38, 0.013), (39, -0.047), (40, 0.016), (41, 0.026), (42, 0.033), (43, 0.009), (44, 0.063), (45, 0.014), (46, -0.031), (47, 0.005), (48, -0.03), (49, -0.01)]
simIndex simValue blogId blogTitle
same-blog 1 0.97885799 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
2 0.79854172 602 high scalability-2009-05-17-Scaling Django Web Apps by Mike Malone
Introduction: Film buffs will recognize Django as a classic 1966 spaghetti western that spawned hundreds of imitators. Web heads will certainly first think of Django as the classic Python based Web framework that has also spawned hundreds of imitators and has become the gold standard framework for the web. Mike Malone, who worked on Pownce, a blogging tool now owned by Six Apart, tells in this very informative EuroDjangoCon presentation how Pownce scaled using Django in the real world. I was surprised to learn how large Pounce was: hundreds of requests/sec, thousands of DB operations/sec, millions of user relationships, millions of notes, and terabytes of static data. Django has a lot of functionality in the box to help you scale, but if you want to scale large it turns out Django has some limitations and Mike tells you what these are and also provides some code to get around them. Mike's talk-although Django specific--will really help anyone creating applications on the web. There's
3 0.76815271 1024 high scalability-2011-04-15-Stuff The Internet Says On Scalability For April 15, 2011
Introduction: Submitted for your reading pleasure... Luxury is an ancient notion. There was once a Chinese mandarin who had himself wakened three times every morning simply for the pleasure of being told it was not yet time to get up . ~Argosy We have a Qutoable Quote machine for you today: @kevinweil : Twitter monthly signups have increased more than 50% since December, and we're now doing well over 150 million Tweets per day. @ChrisShain : Prediction: Black art of query optimization will become black art of #nosql data modeling, for same reasons. Minimize IOs, query time. @ui_matters : Infrastructure as a Service = no hardware headaches. Platform as a Svc = no scalability headaches. SaaS = common dev platform #amchamtech @plcstpierre : Thinking about high scalability stuff... I never thought database stuff can be interesting... @webdz9r : mass scalability for dynamic web content. What took us 8 machines, now take us 1 web and 1 app. @joelvarty : CDN is always an aft
4 0.7621991 1411 high scalability-2013-02-22-Stuff The Internet Says On Scalability For February 22, 2013
Introduction: Hey, it's HighScalability time: Quotable Quotes: @p337er : I have committed some truly horrendous crimes against scalability today. @ErrataRob : doubling performance doesn't double scalability. @rsingel : In 2008 when Yahoo.com linked out, I had a Wired story get 1M visitors in an hour from their homepage. @philiph : Lets solve this scalability problem with a queuing system @jaykreps : Transferring data across data centers? Read this page and go tune your TCP buffer sizes... @gwestr : In which the node community showers schadenfreude upon the rails community for "scalability is not my problem" architectures @pbailis : Makes sense, though I think there's a tradeoff re: coordination and scalability (always homogeneous vs dynamically heterogenous) @pembleton : To summarize Yoav's philosophy: we started as quick as we can and then we accelerated #operationgrandma in #reversim @surfichris : “We chose Heroku because we be
5 0.74914485 1487 high scalability-2013-07-05-Stuff The Internet Says On Scalability For July 5, 2013
Introduction: Hey, it's HighScalability time: (Dolls nerds can nest with ) Quotable Quotes: @Carnage4Life : "Google uses Bayesian filtering the way Microsoft uses the if statement" - http://www.joelonsoftware.com/items/2005/10/17.html … <= finally at the point where I get this @etherealmind : You can dramatically improve blog performance by blocking Amazon IP address ranges. Tells you how much information mining is occurring. Randy Bias : Choice is possible only when there’s architectural consistency between public and private cloud infrastructure. Those who focus only on API compatibility are either confused or intentionally misleading people. There is NO API COMPATIBILITY without architectural compatibility. Nassim Nicholas Taleb : Everything that is fragile and still in existence (that is, unbroken), will be harmed more by a certain stressor of intensity X than by k times a stressor of intensity X/k, up to the point of breaking.
6 0.74694842 1080 high scalability-2011-07-15-Stuff The Internet Says On Scalability For July 15, 2011
7 0.74258673 1147 high scalability-2011-11-25-Stuff The Internet Says On Scalability For November 25, 2011
8 0.73450947 1646 high scalability-2014-05-12-4 Architecture Issues When Scaling Web Applications: Bottlenecks, Database, CPU, IO
9 0.72469395 949 high scalability-2010-11-29-Stuff the Internet Says on Scalability For November 29th, 2010
10 0.72094238 869 high scalability-2010-07-30-Hot Scalability Links for July 30, 2010
11 0.71891099 1198 high scalability-2012-02-24-Stuff The Internet Says On Scalability For February 24, 2012
12 0.71859378 1443 high scalability-2013-04-19-Stuff The Internet Says On Scalability For April 19, 2013
13 0.71714228 1283 high scalability-2012-07-13-Stuff The Internet Says On Scalability For July 13, 2012
14 0.71383727 594 high scalability-2009-05-08-Eight Best Practices for Building Scalable Systems
15 0.7076776 835 high scalability-2010-06-03-Hot Scalability Links for June 3, 2010
16 0.70627415 7 high scalability-2007-07-12-FeedBurner Architecture
17 0.70627159 916 high scalability-2010-10-07-Hot Scalability Links For Oct 8, 2010
18 0.70521528 994 high scalability-2011-02-23-This stuff isn't taught, you learn it bit by bit as you solve each problem.
19 0.70452464 1407 high scalability-2013-02-15-Stuff The Internet Says On Scalability For February 15, 2013
20 0.70416641 1516 high scalability-2013-09-13-Stuff The Internet Says On Scalability For September 13, 2013
topicId topicWeight
[(1, 0.09), (2, 0.31), (10, 0.031), (30, 0.052), (61, 0.101), (66, 0.116), (79, 0.145), (85, 0.026), (94, 0.05)]
simIndex simValue blogId blogTitle
1 0.99053442 375 high scalability-2008-09-01-A Scalability checklist?
Introduction: Hi everyone, I'm researching on Scalability for a college paper, and found this site great, but it has too many tips, articles and the like, but I can't see a hierarchical organization of subjects, I would need something like a checklist of things or fields, or technologies to take into account when assesing scalability. So far I've identified these: - Hardware scalability: - scale out - scale up - Cache What types of cache are there? app-level, os-level, network-level, I/O-level? - Load Balancing - DB Clustering Am I missing something important? (I'm sure I am) I don't expect you to give a lecture here, but maybe point some things out, give me some useful links... Thanks!
same-blog 2 0.9697305 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
3 0.95813435 185 high scalability-2007-12-13-Is premature scalation a real disease?
Introduction: Update 3: InfoQ's Big Architecture Up Front - A Case of Premature Scalaculation? twines several different threads on the topic together into a fine noose. Update 2: Kevin says the biggest problems he sees with startups is they need to scale their backend (no, the other one). Update: My bad. It's hard to sell scalability so just forget it. The premise of Startups and The Problem Of Premature Scalaculation and Don’t scale: 99.999% uptime is for Wal-Mart is that you shouldn't spend precious limited resources worrying about scaling before you've first implemented the functionality that will make you successful enough to have scaling problems in the first place. It's kind of an embodied life force model of system creation. Energy is scarce so any parasites siphoning off energy must be hunted down and destroyed so the body has its best chance of survival. Is this really how it works? If I ever believed this I certainly don't believe it anymore. The world has c
4 0.94554287 622 high scalability-2009-06-08-Distribution of queries per second
Introduction: We need to measure the number of queries-per-second our site gets for capacity planning purposes. Obviously, we need to provision the site based on the peak QPS, not average QPS. There will always be some spikes in traffic, though, where for one particular second we get a really huge number of queries. It's ok if site performance slightly degrades during that time. So what I'd really like to do is estimate the *near* peak QPS based on average or median QPS. Near peak might be defined as the QPS that I get at the 95th percentile of the busiest seconds during the day. My guess is that this is similar to what ISPs do when they measure your bandwidth usage and then charge for usage over the 95th percentile. What we've done is analyzed our logs, counted the queries executed during each second during the day, sorted from the busiest seconds to the least busy ones, and graphed it. What you get is a histogram that steeply declines and flattens out near zero. Does anyone know if there is a
5 0.94420975 76 high scalability-2007-08-29-Skype Failed the Boot Scalability Test: Is P2P fundamentally flawed?
Introduction: Skype's 220 millions users lost service for a stunning two days. The primary cause for Skype's nightmare (can you imagine the beeper storm that went off?) was a massive global roll-out of a Window's patch triggering the simultaneous reboot of millions of machines across the globe. The secondary cause was a bug in Skype's software that prevented "self-healing" in the face of such attacks. The flood of log-in requests and a lack of "peer-to-peer resources" melted their system. Who's fault is it? Is Skype to blame? Is Microsoft to blame? Or is the peer-to-peer model itself fundamentally flawed in some way? Let's be real, how could Skype possibly test booting 220 million servers over a random configuration of resources? Answer: they can't. Yes, it's Skype's responsibility, but they are in a bit of a pickle on this one. The boot scenario is one of the most basic and one of the most difficult scalability scenarios to plan for and test. You can't simulate the viciousness of real-life
6 0.94344914 533 high scalability-2009-03-11-The Implications of Punctuated Scalabilium for Website Architecture
7 0.94313771 661 high scalability-2009-07-25-Latency is Everywhere and it Costs You Sales - How to Crush it
9 0.94272119 1017 high scalability-2011-04-06-Netflix: Run Consistency Checkers All the time to Fixup Transactions
10 0.94231981 1509 high scalability-2013-08-30-Stuff The Internet Says On Scalability For August 30, 2013
11 0.94182521 1439 high scalability-2013-04-12-Stuff The Internet Says On Scalability For April 12, 2013
12 0.94150847 1266 high scalability-2012-06-18-Google on Latency Tolerant Systems: Making a Predictable Whole Out of Unpredictable Parts
13 0.94040477 589 high scalability-2009-05-05-Drop ACID and Think About Data
14 0.93954372 849 high scalability-2010-06-28-VoltDB Decapitates Six SQL Urban Myths and Delivers Internet Scale OLTP in the Process
15 0.93941677 628 high scalability-2009-06-13-Neo4j - a Graph Database that Kicks Buttox
16 0.93924963 1460 high scalability-2013-05-17-Stuff The Internet Says On Scalability For May 17, 2013
17 0.9389149 714 high scalability-2009-10-02-HighScalability has Moved to Squarespace.com!
18 0.93864894 119 high scalability-2007-10-10-WAN Accelerate Your Way to Lightening Fast Transfers Between Data Centers
19 0.93839836 1010 high scalability-2011-03-24-Strategy: Disk Backup for Speed, Tape Backup to Save Your Bacon, Just Ask Google
20 0.93829173 252 high scalability-2008-02-18-limit on the number of databases open