high_scalability high_scalability-2008 high_scalability-2008-285 knowledge-graph by maker-knowledge-mining
Source: html
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.
sentIndex sentText sentNum sentScore
1 0' applications and their rich content and interaction, we expect our applications to increasingly make use of CSS and JavaScript. [sent-3, score-1.176]
2 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. [sent-4, score-2.572]
3 In practice, this means a combination of making our content as small and fast to download as possible, while avoiding unnecessarily refetching unmodified resources. [sent-5, score-1.627]
wordName wordTfidf (topN-words)
[('unmodified', 0.315), ('optimum', 0.301), ('cal', 0.301), ('snappy', 0.29), ('unnecessarily', 0.281), ('content', 0.266), ('render', 0.197), ('sure', 0.193), ('css', 0.191), ('interaction', 0.186), ('increasingly', 0.173), ('avoiding', 0.171), ('applications', 0.168), ('rich', 0.143), ('making', 0.141), ('delivering', 0.14), ('practice', 0.138), ('comments', 0.137), ('nature', 0.133), ('optimize', 0.126), ('download', 0.125), ('combination', 0.118), ('expect', 0.117), ('nice', 0.107), ('size', 0.098), ('required', 0.098), ('page', 0.089), ('make', 0.082), ('possible', 0.079), ('means', 0.077), ('small', 0.072), ('fast', 0.061), ('use', 0.059), ('lot', 0.05), ('good', 0.047), ('web', 0.041), ('need', 0.039)]
simIndex simValue blogId blogTitle
same-blog 1 1.0 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.
2 0.16030394 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
3 0.12179486 282 high scalability-2008-03-18-Database War Stories #3: Flickr
Introduction: [Tim O'Reilly] Continuing my series of queries about how "Web 2.0" companies used databases, I asked Cal Henderson of Flickr to tell me "how the folksonomy model intersects with the traditional database. How do you manage a tag cloud?"
4 0.10478229 856 high scalability-2010-07-12-Creating Scalable Digital Libraries
Introduction: Like many other media content providers, libraries and museums are increasingly moving their content onto the Web. While the move itself is no easy process (with digitization, web development, and training costs), being able to successfully deliver content to a wide audience is an ongoing concern, particularly for large libraries. Much of the concern is financial, as most libraries do not have the internal budget or outside investors that for-profit businesses enjoy. Even large university libraries will face serious budget constraints that even other university departments, such as science and technology would not face. Creating a scalable infrastructure and also distributing a large digital collection that can handle multiple requests, requires planning that many librarians have not even imagined. They must stop thinking in terms of "one-item-per-customer" and start thinking in terms of numerous users accessing the same information simultaneously. Content Delivery Network
5 0.10182792 382 high scalability-2008-09-09-Content Delivery Networks (CDN) – a comprehensive list of providers
Introduction: We build web applications…and there are plenty of them around. Now, if we hit the jackpot and our application becomes very popular, traffic goes up, and our servers are brought down by the hordes of people coming to our website. What do we do in that situation? Of course, I am not talking here about the kind of traffic Digg, Yahoo Buzz or other social media sites can bring to a website, which is temporary overnight traffic, or a website which uses cloud computing like Amazon EC2 service, MediaTemple Grid Service or Mosso Hosting Cloud service. I am talking about traffic that consistently increases over time as the service achieves success. Google.com, Yahoo.com, Myspace.com, Facebook.com, Plentyoffish.com, Linkedin.com, Youtube.com and others are examples of services which have constant high traffic. Knowing that users want speed from their applications, these services will always use a Content Delivery Network (CDN) to deliver that speed. What is a Content Delivery Ne
6 0.093815491 617 high scalability-2009-06-04-New Book: Even Faster Web Sites: Performance Best Practices for Web Developers
7 0.08751905 576 high scalability-2009-04-21-What CDN would you recommend?
8 0.08740548 136 high scalability-2007-10-28-Scaling Early Stage Startups
9 0.084357597 274 high scalability-2008-03-12-YouTube Architecture
10 0.080573454 396 high scalability-2008-09-26-Lucasfilm: The Real Magic is in the Data Center
11 0.079306021 1068 high scalability-2011-06-27-TripAdvisor Architecture - 40M Visitors, 200M Dynamic Page Views, 30TB Data
12 0.078306586 1401 high scalability-2013-02-06-Super Bowl Advertisers Ready for the Traffic? Nope..It's Lights Out.
13 0.077772684 356 high scalability-2008-07-22-Scaling Bumper Sticker: A 1 Billion Page Per Month Facebook RoR App
14 0.074325643 176 high scalability-2007-12-07-Synchronizing databases in different geographic locations
15 0.07335484 377 high scalability-2008-09-03-SMACKDOWN :: Who are the Open Source Content Management System (CMS) market leaders in 2008?
16 0.072336316 204 high scalability-2008-01-08-Virus Scanning for Uploaded content
topicId topicWeight
[(0, 0.099), (1, 0.01), (2, 0.001), (3, -0.054), (4, -0.016), (5, -0.028), (6, -0.027), (7, 0.015), (8, -0.009), (9, 0.044), (10, -0.003), (11, -0.018), (12, -0.051), (13, -0.005), (14, 0.002), (15, -0.026), (16, -0.007), (17, -0.0), (18, 0.045), (19, -0.087), (20, -0.045), (21, 0.011), (22, 0.032), (23, 0.01), (24, -0.023), (25, 0.015), (26, -0.011), (27, -0.023), (28, 0.005), (29, 0.003), (30, -0.032), (31, 0.043), (32, 0.062), (33, -0.005), (34, -0.015), (35, -0.052), (36, 0.033), (37, 0.041), (38, -0.009), (39, -0.039), (40, -0.022), (41, -0.008), (42, -0.001), (43, 0.032), (44, -0.004), (45, 0.001), (46, -0.003), (47, -0.034), (48, -0.051), (49, 0.023)]
simIndex simValue blogId blogTitle
same-blog 1 0.97174573 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.
2 0.80609328 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.77589995 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
4 0.76125777 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.70773542 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.
7 0.68965572 204 high scalability-2008-01-08-Virus Scanning for Uploaded content
8 0.67544705 194 high scalability-2007-12-26-Golden rule of web caching
9 0.66941208 31 high scalability-2007-07-26-Product: Symfony a Web Framework
10 0.6670602 1102 high scalability-2011-08-22-Strategy: Run a Scalable, Available, and Cheap Static Site on S3 or GitHub
11 0.66484004 1401 high scalability-2013-02-06-Super Bowl Advertisers Ready for the Traffic? Nope..It's Lights Out.
12 0.66162461 382 high scalability-2008-09-09-Content Delivery Networks (CDN) – a comprehensive list of providers
13 0.65748924 856 high scalability-2010-07-12-Creating Scalable Digital Libraries
14 0.65726781 1427 high scalability-2013-03-20-Dart - Is it the Future of the Web?
15 0.65116483 47 high scalability-2007-07-30-Product: Yslow to speed up your web pages
16 0.64461553 1533 high scalability-2013-10-16-Interview With Google's Ilya Grigorik On His New Book: High Performance Browser Networking
17 0.6401059 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
18 0.63276666 617 high scalability-2009-06-04-New Book: Even Faster Web Sites: Performance Best Practices for Web Developers
19 0.63021123 39 high scalability-2007-07-30-Product: Akamai
20 0.62853932 1321 high scalability-2012-09-12-Using Varnish for Paywalls: Moving Logic to the Edge
topicId topicWeight
[(1, 0.199), (2, 0.181), (12, 0.392), (61, 0.077)]
simIndex simValue blogId blogTitle
1 0.88941908 209 high scalability-2008-01-12-Gandi.net, french registrar launches in granular server resources.
Introduction: Gandi.net, a French domain registrar has launched a very flexible dynamic resource allocated VPS service.
2 0.80284554 278 high scalability-2008-03-16-Product: GlusterFS
Introduction: Adapted from their website: GlusterFS is a clustered file-system capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware such as x86-64 server with SATA-II RAID and Infiniband HBA). Cluster file systems are still not mature for enterprise market. They are too complex to deploy and maintain though they are extremely scalable and cheap. Can be entirely built out of commodity OS and hardware. GlusterFS hopes to solves this problem. GlusterFS achieved 35 GBps read throughput . The GlusterFS Aggregated I/O Benchmark was performed on 64 bricks clustered storage system over 10 Gbps Infiniband interconnect. A cluster of 220 clients pounded the storage system with multiple dd (disk-dump) instances, each reading / writing a 1 GB file with 1MB block size. GlusterFS was configured with unify translator and round-robin scheduler
3 0.75818551 82 high scalability-2007-09-06-Why doesn't anyone use j2ee?
Introduction: From a reader: > Was reading through your very interesting/useful site. >Most of the architectures are non j2ee-Does that mean that >there aren't enough websites that are scalable(with youtube > like userbase) built with j2ee tech-would like to know if there > are any and their architecture as >well. eBay uses Java, but in a very pragmatic way. They use servlets, an application server, the JDK, and they do the rest themselves. They skip JSP, entity beans, and JMS. When you need to scale putting all your eggs in one basket is a risky strategy. Why use JSP when you can do better? When use entity beans when you can do better? Use servlets because they are a very effective way of handling http requests. Use Java because it is fast, runs everywhere, and has a boat load of libraries you can use to build your build your custom system. Probably the major reason J2EE is absentee is simply LAMP. LAMP is just so incredibly functional for most 2-tier shared nothing site
same-blog 4 0.74837351 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.70427746 3 high scalability-2007-07-09-LiveJournal Architecture
Introduction: A fascinating and detailed story of how LiveJournal evolved their system to scale. LiveJournal was an early player in the free blog service race and faced issues from quickly adding a large number of users. Blog posts come fast and furious which causes a lot of writes and writes are particularly hard to scale. Understanding how LiveJournal faced their scaling problems will help any aspiring website builder. Site: http://www.livejournal.com/ Information Sources LiveJournal - Behind The Scenes Scaling Storytime Google Video Tokyo Video 2005 version Platform Linux MySql Perl Memcached MogileFS Apache What's Inside? Scaling from 1, 2, and 4 hosts to cluster of servers. Avoid single points of failure. Using MySQL replication only takes you so far. Becoming IO bound kills scaling. Spread out writes and reads for more parallelism. You can't keep adding read slaves and scale. Shard storage approach, using DRBD, for maxim
6 0.70386082 490 high scalability-2009-01-12-Getting ready for the cloud
7 0.67399234 161 high scalability-2007-11-20-Product: SmartFrog a Distributed Configuration and Deployment Framework
8 0.66605484 1352 high scalability-2012-10-31-Gone Fishin': LiveJournal Architecture
9 0.65447456 886 high scalability-2010-08-24-21 Quality Screencasts on Scaling Rails
10 0.57496619 727 high scalability-2009-10-25-Is Your Data Really Secured?
11 0.56886601 1517 high scalability-2013-09-16-The Hidden DNS Tax - Cascading Timeouts and Errors
12 0.56778014 701 high scalability-2009-09-10-When optimizing - don't forget the Java Virtual Machine (JVM)
13 0.56709623 1349 high scalability-2012-10-29-Gone Fishin': Welcome to High Scalability
14 0.56687033 887 high scalability-2010-08-24-Sponsored Post: deviantART, Okta, EzRez, Cloud Sigma, ManageEngine, Site24x7
15 0.56637043 407 high scalability-2008-10-10-The Art of Capacity Planning: Scaling Web Resources
17 0.56619298 866 high scalability-2010-07-27-Sponsored Post: Okta, EzRez, VoltDB, Digg, Cloud Sigma, Applications Manager, Site24x7
18 0.56567097 833 high scalability-2010-06-01-Sponsored Post: Get Your High Scalability Fix at Digg
19 0.56436455 983 high scalability-2011-02-02-Piccolo - Building Distributed Programs that are 11x Faster than Hadoop
20 0.56348032 276 high scalability-2008-03-15-New Website Design Considerations