high_scalability high_scalability-2008 high_scalability-2008-291 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Update: Nice explanation in The importance of bandwidth versus latency of how long latencies cause cascading delays in resource loading. Doloto tries to optimize how resources are loaded. Twenty new rules have been added to the original 14 rules for sizzling web performance. Part of scalability is worrying about performance too. The front-end is where 80-90% of end-user response time is spent and following these best practices improved the performance of Yahoo! properties by 25-50%. The rules are divided into server, content, cookie, JavaScript, CSS, images, and mobile categories. The new rules are: Flush the buffer early [server] Use GET for AJAX requests [server] Post-load components [content] Preload components [content] Reduce the number of DOM elements [content] Split components across domains [content] Minimize the number of iframes [content] No 404s [content] Reduce cookie size [cookie] Use cookie-free domains for components [coo
sentIndex sentText sentNum sentScore
1 Update: Nice explanation in The importance of bandwidth versus latency of how long latencies cause cascading delays in resource loading. [sent-1, score-0.449]
2 Doloto tries to optimize how resources are loaded. [sent-2, score-0.154]
3 Twenty new rules have been added to the original 14 rules for sizzling web performance. [sent-3, score-0.383]
4 The front-end is where 80-90% of end-user response time is spent and following these best practices improved the performance of Yahoo! [sent-5, score-0.181]
5 The rules are divided into server, content, cookie, JavaScript, CSS, images, and mobile categories. [sent-7, score-0.347]
6 ico small and cacheable [images] Keep components under 25K [mobile] Pack components into a multipart document [mobile] Thanks to Simon Willison for the link. [sent-9, score-0.814]
wordName wordTfidf (topN-words)
[('images', 0.386), ('cookie', 0.372), ('css', 0.311), ('content', 0.253), ('components', 0.252), ('dom', 0.222), ('javascript', 0.163), ('optimize', 0.154), ('domains', 0.148), ('multipart', 0.137), ('preload', 0.137), ('sizzling', 0.137), ('sprites', 0.137), ('mobile', 0.135), ('rules', 0.123), ('minimize', 0.117), ('cacheable', 0.114), ('pack', 0.108), ('flush', 0.106), ('handlers', 0.102), ('import', 0.102), ('theoriginal', 0.1), ('iframes', 0.093), ('inthe', 0.091), ('divided', 0.089), ('cascading', 0.087), ('delays', 0.085), ('reduce', 0.084), ('filters', 0.083), ('importance', 0.082), ('worrying', 0.081), ('elements', 0.076), ('ajax', 0.075), ('buffer', 0.072), ('html', 0.07), ('versus', 0.069), ('latencies', 0.068), ('properties', 0.066), ('thanks', 0.064), ('improved', 0.063), ('yahoo', 0.061), ('document', 0.059), ('spent', 0.059), ('split', 0.059), ('practices', 0.059), ('explanation', 0.058), ('link', 0.057), ('server', 0.055), ('smart', 0.051), ('number', 0.05)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999988 291 high scalability-2008-03-29-20 New Rules for Faster Web Pages
Introduction: Update: Nice explanation in The importance of bandwidth versus latency of how long latencies cause cascading delays in resource loading. Doloto tries to optimize how resources are loaded. Twenty new rules have been added to the original 14 rules for sizzling web performance. Part of scalability is worrying about performance too. The front-end is where 80-90% of end-user response time is spent and following these best practices improved the performance of Yahoo! properties by 25-50%. The rules are divided into server, content, cookie, JavaScript, CSS, images, and mobile categories. The new rules are: Flush the buffer early [server] Use GET for AJAX requests [server] Post-load components [content] Preload components [content] Reduce the number of DOM elements [content] Split components across domains [content] Minimize the number of iframes [content] No 404s [content] Reduce cookie size [cookie] Use cookie-free domains for components [coo
2 0.20296265 319 high scalability-2008-05-14-Scaling an image upload service
Introduction: Hi, First of all I want to to say that this is an extremely interesting and informative website. i have enjoyed reading the various posts on how the big sites scale to meet the needs of their customers. The service we are developing is a webcam service. The client application sends images to the server via HTTP POST and they are saved in folder specified by the users id. When a new image is sent to the server it will overwrite the current image. Users can then view the images via our web server. Ideally we want the images to upload as quickly as possible and allow users to view them as quickly as possible. Would I be correct to assume that when the number of uploading clients exceeds the capability of the server the only way to scale is to add more hardware. Also I assume that to use HTTP accelerator caches will not speed up viewing the images as the new images will invalidate the cache. I appreciate any input on the subject.
3 0.1633199 506 high scalability-2009-02-03-10 More Rules for Even Faster Websites
Introduction: Update: How-To Minimize Load Time for Fast User Experiences . Shows how to analyze the bottlenecks preventing websites and blogs from loading quickly and how to resolve them. 80-90% of the end-user response time is spent on the frontend, so it makes sense to concentrate efforts there before heroically rewriting the backend. Take a shower before buying a Porsche, if you know what I mean. Steve Souders, author of High Performance Websites and Yslow , has ten more best practices to speed up your website : Split the initial payload Load scripts without blocking Don’t scatter scripts Split dominant content domains Make static content cookie-free Reduce cookie weight Minify CSS Optimize images Use iframes sparingly To www or not to www Sadly, according to String Theory, there are only 26.7 rules left, so get them while they're still in our dimension. Here are slides on the first few rules. Love the speeding dog slide. That's exactly what my dog looks like trav
4 0.16030394 285 high scalability-2008-03-19-Serving JavaScript Fast
Introduction: Cal Henderson writes at thinkvitamin.com : "With our so-called "Web 2.0' applications and their rich content and interaction, we expect our applications to increasingly make use of CSS and JavaScript. To make sure these applications are nice and snappy to use, we need to optimize the size and nature of content required to render the page, making sure we’re delivering the optimum experience. In practice, this means a combination of making our content as small and fast to download as possible, while avoiding unnecessarily refetching unmodified resources." A lot of good comments too.
5 0.15658796 261 high scalability-2008-02-25-Make Your Site Run 10 Times Faster
Introduction: This is what Mike Peters says he can do : make your site run 10 times faster. His test bed is "half a dozen servers parsing 200,000 pages per hour over 40 IP addresses, 24 hours a day." Before optimization CPU spiked to 90% with 50 concurrent connections. After optimization each machine "was effectively handling 500 concurrent connections per second with CPU at 8% and no degradation in performance." Mike identifies six major bottlenecks: Database write access (read is cheaper) Database read access PHP, ASP, JSP and any other server side scripting Client side JavaScript Multiple/Fat Images, scripts or css files from different domains on your page Slow keep-alive client connections, clogging your available sockets Mike's solutions: Switch all database writes to offline processing Minimize number of database read access to the bare minimum. No more than two queries per page. Denormalize your database and Optimize MySQL tables Implement MemCached and cha
6 0.1563991 653 high scalability-2009-07-08-Servers Component - How to choice and build perfect server
7 0.14781076 1268 high scalability-2012-06-20-Ask HighScalability: How do I organize millions of images?
8 0.14214481 5 high scalability-2007-07-10-mixi.jp Architecture
9 0.13646208 617 high scalability-2009-06-04-New Book: Even Faster Web Sites: Performance Best Practices for Web Developers
10 0.13086237 585 high scalability-2009-04-29-How to choice and build perfect server
11 0.13003871 1321 high scalability-2012-09-12-Using Varnish for Paywalls: Moving Logic to the Edge
12 0.12797253 100 high scalability-2007-09-26-Use a CDN to Instantly Improve Your Website's Performance by 20% or More
13 0.11944253 1259 high scalability-2012-06-07-3 Secrets to Lightning Fast Mobile Design at Instagram
14 0.11826874 1333 high scalability-2012-10-04-LinkedIn Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster
15 0.11824888 1068 high scalability-2011-06-27-TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data
17 0.10944589 660 high scalability-2009-07-21-Paper: Parallelizing the Web Browser
18 0.1093013 273 high scalability-2008-03-09-Best Practices for Speeding Up Your Web Site
19 0.10740419 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
topicId topicWeight
[(0, 0.104), (1, 0.048), (2, -0.018), (3, -0.098), (4, -0.022), (5, -0.049), (6, -0.004), (7, 0.031), (8, -0.021), (9, 0.082), (10, -0.036), (11, -0.046), (12, -0.027), (13, -0.05), (14, -0.007), (15, 0.021), (16, 0.011), (17, 0.037), (18, 0.073), (19, -0.128), (20, -0.037), (21, 0.004), (22, -0.012), (23, -0.03), (24, -0.019), (25, 0.028), (26, -0.026), (27, -0.019), (28, 0.001), (29, 0.01), (30, -0.056), (31, 0.096), (32, 0.066), (33, 0.043), (34, -0.009), (35, -0.084), (36, 0.07), (37, 0.086), (38, -0.034), (39, -0.135), (40, -0.03), (41, -0.082), (42, -0.039), (43, 0.015), (44, -0.082), (45, -0.059), (46, 0.05), (47, -0.021), (48, -0.051), (49, 0.149)]
simIndex simValue blogId blogTitle
same-blog 1 0.98430979 291 high scalability-2008-03-29-20 New Rules for Faster Web Pages
Introduction: Update: Nice explanation in The importance of bandwidth versus latency of how long latencies cause cascading delays in resource loading. Doloto tries to optimize how resources are loaded. Twenty new rules have been added to the original 14 rules for sizzling web performance. Part of scalability is worrying about performance too. The front-end is where 80-90% of end-user response time is spent and following these best practices improved the performance of Yahoo! properties by 25-50%. The rules are divided into server, content, cookie, JavaScript, CSS, images, and mobile categories. The new rules are: Flush the buffer early [server] Use GET for AJAX requests [server] Post-load components [content] Preload components [content] Reduce the number of DOM elements [content] Split components across domains [content] Minimize the number of iframes [content] No 404s [content] Reduce cookie size [cookie] Use cookie-free domains for components [coo
2 0.73902476 506 high scalability-2009-02-03-10 More Rules for Even Faster Websites
Introduction: Update: How-To Minimize Load Time for Fast User Experiences . Shows how to analyze the bottlenecks preventing websites and blogs from loading quickly and how to resolve them. 80-90% of the end-user response time is spent on the frontend, so it makes sense to concentrate efforts there before heroically rewriting the backend. Take a shower before buying a Porsche, if you know what I mean. Steve Souders, author of High Performance Websites and Yslow , has ten more best practices to speed up your website : Split the initial payload Load scripts without blocking Don’t scatter scripts Split dominant content domains Make static content cookie-free Reduce cookie weight Minify CSS Optimize images Use iframes sparingly To www or not to www Sadly, according to String Theory, there are only 26.7 rules left, so get them while they're still in our dimension. Here are slides on the first few rules. Love the speeding dog slide. That's exactly what my dog looks like trav
3 0.73044181 285 high scalability-2008-03-19-Serving JavaScript Fast
Introduction: Cal Henderson writes at thinkvitamin.com : "With our so-called "Web 2.0' applications and their rich content and interaction, we expect our applications to increasingly make use of CSS and JavaScript. To make sure these applications are nice and snappy to use, we need to optimize the size and nature of content required to render the page, making sure we’re delivering the optimum experience. In practice, this means a combination of making our content as small and fast to download as possible, while avoiding unnecessarily refetching unmodified resources." A lot of good comments too.
4 0.69958413 100 high scalability-2007-09-26-Use a CDN to Instantly Improve Your Website's Performance by 20% or More
Introduction: If you have a lot of static content to store and you aren't looking forward to setting up and maintaining your own giganto SAN, maybe you can push off a lot of the hard lifting to a CDN? Jesse Robbins at O'Reilly Radar posts that you have a lot more options now because the number of Content Distribution Networks have doubled since last year . In fact, Dan Rayburn says there are now 28 CDN providers in the market. Hopefully you can find reasonable pricing at one of them. Other than easing your burden, why might a CDN work for you? Because it makes your site faster and customers like that. How can a CDN so dramatically improve your site's performance? Steve Saunders, author of High Performance Web Sites: Essential Knowledge for Front-End Engineers , has using a CDN has one of his "Thirteen Simple Rules for Speeding Up Your Web Site." About CDNs Steve says: Remember that 80-90% of the end-user response time is spent downloading all the components in
5 0.68052036 135 high scalability-2007-10-27-.Net2 and AJAX scalability?
Introduction: Am I mad to cons i der using .Net2 and AJAX for a high-scalabi l ity app l ication? In case you wonder why, it's the legacy of a webs i te bui l t on IIS and .Net 1.1, and we're look i ng for ways to make the content more attractive and interact i ve. In this case, it's a medical image l i brary being shared by a few Wikis and on l ine coursework for medica l students ( < 15K users) and doctors ( < 150K users) But I'm worr i ed about the performance overhead. We a l ready have a performance prob l em because of personal i sing the content for users according to their type (student or doctor), and for doctors, their grade and special i ty.
6 0.65110332 319 high scalability-2008-05-14-Scaling an image upload service
7 0.58496946 1268 high scalability-2012-06-20-Ask HighScalability: How do I organize millions of images?
8 0.58433014 47 high scalability-2007-07-30-Product: Yslow to speed up your web pages
9 0.58193976 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
10 0.57936275 1401 high scalability-2013-02-06-Super Bowl Advertisers Ready for the Traffic? Nope..It's Lights Out.
11 0.56637764 273 high scalability-2008-03-09-Best Practices for Speeding Up Your Web Site
12 0.56542349 856 high scalability-2010-07-12-Creating Scalable Digital Libraries
13 0.5622288 800 high scalability-2010-03-26-Strategy: Caching 404s Saved the Onion 66% on Server Time
14 0.56048352 942 high scalability-2010-11-15-Strategy: Biggest Performance Impact is to Reduce the Number of HTTP Requests
15 0.55644989 382 high scalability-2008-09-09-Content Delivery Networks (CDN) – a comprehensive list of providers
16 0.55589914 1333 high scalability-2012-10-04-LinkedIn Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster
17 0.53632134 665 high scalability-2009-07-29-Strategy: Let Google and Yahoo Host Your Ajax Library - For Free
18 0.53317112 617 high scalability-2009-06-04-New Book: Even Faster Web Sites: Performance Best Practices for Web Developers
19 0.52822465 1427 high scalability-2013-03-20-Dart - Is it the Future of the Web?
20 0.52373159 377 high scalability-2008-09-03-SMACKDOWN :: Who are the Open Source Content Management System (CMS) market leaders in 2008?
topicId topicWeight
[(1, 0.108), (2, 0.165), (17, 0.025), (30, 0.156), (32, 0.225), (47, 0.04), (61, 0.063), (79, 0.094)]
simIndex simValue blogId blogTitle
same-blog 1 0.89626575 291 high scalability-2008-03-29-20 New Rules for Faster Web Pages
Introduction: Update: Nice explanation in The importance of bandwidth versus latency of how long latencies cause cascading delays in resource loading. Doloto tries to optimize how resources are loaded. Twenty new rules have been added to the original 14 rules for sizzling web performance. Part of scalability is worrying about performance too. The front-end is where 80-90% of end-user response time is spent and following these best practices improved the performance of Yahoo! properties by 25-50%. The rules are divided into server, content, cookie, JavaScript, CSS, images, and mobile categories. The new rules are: Flush the buffer early [server] Use GET for AJAX requests [server] Post-load components [content] Preload components [content] Reduce the number of DOM elements [content] Split components across domains [content] Minimize the number of iframes [content] No 404s [content] Reduce cookie size [cookie] Use cookie-free domains for components [coo
2 0.83509982 363 high scalability-2008-08-12-Strategy: Limit The New, Not The Old
Introduction: One of the most popular and effective scalability strategies is to impose limits ( GAE Quotas , Fotolog , Facebook ) as a means of protecting a website against service destroying traffic spikes . Twitter will reportedly limit the number followers to 2,000 in order to thwart follow spam. This may also allow Twitter to make some bank by going freemium and charging for adding more followers. Agree or disagree with Twitter's strategies, the more interesting aspect for me is how do you introduce new policies into an already established ecosystem? One approach is the big bang. Introduce all changes at once and let everyone adjust. If users don't like it they can move on. The hope is, however, most users won't be impacted by the changes and that those who are will understand it's all for the greater good of their beloved service. Casualties are assumed, but the damage will probably be minor. Now in Twitter's case the people with the most followers tend to be o
3 0.82877898 287 high scalability-2008-03-24-Advertise
Introduction: If you would like to advertise on this site please contact me at todd@possibility.com . We can work out the details over email. Thanks
4 0.81212354 251 high scalability-2008-02-18-How to deal with an I-O bottleneck to disk?
Introduction: A site I'm working with has an I/O bottleneck. They're using a static server to deliver all of the pictures/video content/zip downloads ecetera but now that the bandwith out of that server is approaching 50Mbit/second the latency on serving small files has increased to become unacceptable. I'm curious how other people have dealt with this situation. Seperating into two different servers would require a significant change to the sites architecutre (because the premise is that all uploads go into one server, all subdirectorie are created in one directory, etc.) and may not really solve the problem.
5 0.80086797 1193 high scalability-2012-02-16-A Short on the Pinterest Stack for Handling 3+ Million Users
Introduction: Pinterest co-founder Paul Sciarra shared a bit about their stack on Quora: Python + heavily-modified Django at the application layer Tornado and (very selectively) node.js as web-servers. Memcached and membase / redis for object- and logical-caching, respectively. RabbitMQ as a message queue. Nginx, HAproxy and Varnish for static-delivery and load-balancing. Persistent data storage using MySQL. MrJob on EMR for map-reduce. Git. Alex Popescu has created a cool diagram of the setup and provided some thoughtful analysis as well.
6 0.79079956 648 high scalability-2009-07-02-It Must be Crap on Relational Dabases Week
7 0.78292584 523 high scalability-2009-02-25-Relating business, systems & technology during turbulent time -By John Zachman
8 0.74881601 1459 high scalability-2013-05-16-Paper: Warp: Multi-Key Transactions for Key-Value Stores
9 0.74867606 261 high scalability-2008-02-25-Make Your Site Run 10 Times Faster
10 0.74602455 783 high scalability-2010-02-24-Hot Scalability Links for February 24, 2010
11 0.74332935 831 high scalability-2010-05-26-End-To-End Performance Study of Cloud Services
12 0.74001831 500 high scalability-2009-01-22-Heterogeneous vs. Homogeneous System Architectures
13 0.73910171 336 high scalability-2008-05-31-Biggest Under Reported Story: Google's BigTable Costs 10 Times Less than Amazon's SimpleDB
14 0.73358303 308 high scalability-2008-04-22-Simple NFS failover solution with symbolic link?
15 0.73223323 552 high scalability-2009-04-01-Art of scalability (1) - Scalability principles
16 0.73117548 1284 high scalability-2012-07-16-Cinchcast Architecture - Producing 1,500 Hours of Audio Every Day
17 0.73104906 16 high scalability-2007-07-16-Book: High Performance MySQL
18 0.72878635 263 high scalability-2008-02-27-Product: System Imager - Automate Deployment and Installs
19 0.72365975 917 high scalability-2010-10-08-4 Scalability Themes from Surgecon