high_scalability high_scalability-2010 high_scalability-2010-941 knowledge-graph by maker-knowledge-mining

941 high scalability-2010-11-15-How Google's Instant Previews Reduces HTTP Requests


meta infos for this blog

Source: html

Introduction: In a strange case of synchronicity, Google just published Instant Previews: Under the hood , a very well written blog post by Matías Pelenur of the Instant Previews team, giving some fascinating inside details on how Google implemented Instant Previews . It's syncronicty because I had just posted  Strategy: Biggest Performance Impact Is To Reduce The Number Of HTTP Requests  and one of the major ideas behind the design Instant Previews is to reduce the number of HTTP requests through a few well chosen tricks. Cosmic! Some of what Google does to reduce HTTP requests: Data URIs , which are are base64 encodings of image data, are used instead of static images that are served from the server. This means the whole preview can be pieced together from image slices in one request as both the data and the image are returned in the same request. Google found that even though base64 encoding adds about 33% to the size of the image, tests showed that gzip-compressed data URIs are compara


Summary: the most important sentenses genereted by tfidf model

sentIndex sentText sentNum sentScore

1 In a strange case of synchronicity, Google just published Instant Previews: Under the hood , a very well written blog post by Matías Pelenur of the Instant Previews team, giving some fascinating inside details on how Google implemented Instant Previews . [sent-1, score-0.543]

2 It's syncronicty because I had just posted  Strategy: Biggest Performance Impact Is To Reduce The Number Of HTTP Requests  and one of the major ideas behind the design Instant Previews is to reduce the number of HTTP requests through a few well chosen tricks. [sent-2, score-0.793]

3 Some of what Google does to reduce HTTP requests: Data URIs , which are are base64 encodings of image data, are used instead of static images that are served from the server. [sent-4, score-0.77]

4 This means the whole preview can be pieced together from image slices in one request as both the data and the image are returned in the same request. [sent-5, score-1.217]

5 Google found that even though base64 encoding adds about 33% to the size of the image, tests showed that gzip-compressed data URIs are comparable in size to the original JPEGs. [sent-6, score-0.832]

6 Using JSONP and data URIs reduces the number of requests made, but they are also cacheable by the browser, which should make page refreshes instantaneous. [sent-7, score-0.705]

7 Obviously caching also reduces the number of HTTP requests. [sent-8, score-0.261]


similar blogs computed by tfidf model

tfidf for this blog:

wordName wordTfidf (topN-words)

[('previews', 0.473), ('uris', 0.435), ('image', 0.268), ('requests', 0.213), ('refreshes', 0.168), ('cosmic', 0.168), ('pieced', 0.158), ('instant', 0.157), ('reduce', 0.154), ('http', 0.152), ('encodings', 0.145), ('google', 0.142), ('preview', 0.14), ('reduces', 0.138), ('slices', 0.125), ('number', 0.123), ('comparable', 0.113), ('hood', 0.112), ('encoding', 0.104), ('posted', 0.103), ('size', 0.098), ('showed', 0.094), ('returned', 0.094), ('chosen', 0.092), ('strange', 0.089), ('obviously', 0.085), ('adds', 0.076), ('fascinating', 0.074), ('served', 0.074), ('giving', 0.073), ('browser', 0.069), ('tests', 0.068), ('original', 0.068), ('images', 0.068), ('biggest', 0.065), ('data', 0.063), ('inside', 0.062), ('static', 0.061), ('impact', 0.057), ('well', 0.057), ('blog', 0.054), ('ideas', 0.054), ('strategy', 0.051), ('request', 0.051), ('major', 0.051), ('details', 0.05), ('whole', 0.05), ('though', 0.05), ('behind', 0.049), ('written', 0.045)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.99999994 941 high scalability-2010-11-15-How Google's Instant Previews Reduces HTTP Requests

Introduction: In a strange case of synchronicity, Google just published Instant Previews: Under the hood , a very well written blog post by Matías Pelenur of the Instant Previews team, giving some fascinating inside details on how Google implemented Instant Previews . It's syncronicty because I had just posted  Strategy: Biggest Performance Impact Is To Reduce The Number Of HTTP Requests  and one of the major ideas behind the design Instant Previews is to reduce the number of HTTP requests through a few well chosen tricks. Cosmic! Some of what Google does to reduce HTTP requests: Data URIs , which are are base64 encodings of image data, are used instead of static images that are served from the server. This means the whole preview can be pieced together from image slices in one request as both the data and the image are returned in the same request. Google found that even though base64 encoding adds about 33% to the size of the image, tests showed that gzip-compressed data URIs are compara

2 0.11948384 1333 high scalability-2012-10-04-LinkedIn Moved from Rails to Node: 27 Servers Cut and Up to 20x Faster

Introduction: Update : More background by Ikai Lan, who worked on the mobile server team at LinkedIn, says some facts were left out : the app made "a cross data center request, guys. Running on single-threaded Rails servers (every request blocked the entire process), running Mongrel, leaking memory like a sieve." Which explains why any non-blocking approach would be a win. And Ikai, I hope as you do that nobody reads HS and just does what somebody else does without thinking. The goal here is information that you can use to make your own decisions.   Ryan Paul has written an excellent  behind-the-scenes look at LinkedIn’s mobile engineering . While the mobile part of the story--23% mobile usage; focus on simplicity, ease of use, and reliability; using a room metaphor; 30% native, 80% HTML; embedded lightweight HTTP server; single client-app connection--could help guide your mobile strategy, the backend effects of moving from Rails to Node.js may also prove interesting.  After evaluation, some

3 0.11381883 942 high scalability-2010-11-15-Strategy: Biggest Performance Impact is to Reduce the Number of HTTP Requests

Introduction: Low Cost, High Performance, Strong Security: Pick Any Three  by Chris Palmer has a funny and informative presentation where the main message is: reduce the size and frequency of network communications, which will make your pages load faster, which will improve performance enough that you can use HTTPS all the time, which will make you safe and secure on-line, which is a good thing . The benefits of HTTPS for security are overwhelming, but people are afraid of the performance hit. The argument is successfully made that the overhead of HTTPS is low enough that you can afford the cost if you do some basic optimization. Reducing the number of HTTP requests is a good source of low hanging fruit. From the Yahoo UI Blog : Reducing the number of HTTP requests has the biggest impact on reducing response time and is often the easiest performance improvement to make. From the Experience of Gmail :  …we found that there were between fourteen and twenty-four HTTP requests require

4 0.10888127 132 high scalability-2007-10-25-Who can answer or analyze the image store and visit solution about alibaba.com?Thanks

Introduction: Who can answer or analyze the image store and visit solution about alibaba.com?Thanks

5 0.10566898 1266 high scalability-2012-06-18-Google on Latency Tolerant Systems: Making a Predictable Whole Out of Unpredictable Parts

Introduction: In Taming The Long Latency Tail we covered Luiz Barroso ’s exploration of the long tail latency (some operations are really slow) problems generated by large fanout architectures (a request is composed of potentially thousands of other requests). You may have noticed there weren’t a lot of solutions. That’s where a talk I attended, Achieving Rapid Response Times in Large Online Services ( slide deck ), by Jeff Dean , also of Google, comes in: In this talk, I’ll describe a collection of techniques and practices lowering response times in large distributed systems whose components run on shared clusters of machines, where pieces of these systems are subject to interference by other tasks, and where unpredictable latency hiccups are the norm, not the exception. The goal is to use software techniques to reduce variability given the increasing variability in underlying hardware, the need to handle dynamic workloads on a shared infrastructure, and the need to use lar

6 0.094199359 728 high scalability-2009-10-26-Facebook's Memcached Multiget Hole: More machines != More Capacity

7 0.091013983 43 high scalability-2007-07-30-Product: ImageShack

8 0.089491941 960 high scalability-2010-12-20-Netflix: Use Less Chatty Protocols in the Cloud - Plus 26 Fixes

9 0.084148183 319 high scalability-2008-05-14-Scaling an image upload service

10 0.082846522 899 high scalability-2010-09-09-How did Google Instant become Faster with 5-7X More Results Pages?

11 0.081266485 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant

12 0.081112139 1591 high scalability-2014-02-05-Little’s Law, Scalability and Fault Tolerance: The OS is your bottleneck. What you can do?

13 0.079572923 5 high scalability-2007-07-10-mixi.jp Architecture

14 0.076103278 245 high scalability-2008-02-12-Product: rPath - Creating and Managing Virtual Appliances

15 0.075681545 72 high scalability-2007-08-22-Wikimedia architecture

16 0.075665824 263 high scalability-2008-02-27-Product: System Imager - Automate Deployment and Installs

17 0.075546175 242 high scalability-2008-02-07-Looking for good business examples of compaines using Hadoop

18 0.075237177 1615 high scalability-2014-03-19-Strategy: Three Techniques to Survive Traffic Surges by Quickly Scaling Your Site

19 0.074253365 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results

20 0.073081613 981 high scalability-2011-02-01-Google Strategy: Tree Distribution of Requests and Responses


similar blogs computed by lsi model

lsi for this blog:

topicId topicWeight

[(0, 0.102), (1, 0.063), (2, -0.013), (3, -0.038), (4, -0.005), (5, -0.022), (6, 0.037), (7, 0.044), (8, -0.01), (9, 0.04), (10, -0.0), (11, -0.064), (12, 0.009), (13, -0.03), (14, -0.003), (15, -0.019), (16, -0.047), (17, -0.05), (18, 0.109), (19, -0.054), (20, 0.021), (21, 0.01), (22, 0.021), (23, -0.059), (24, -0.017), (25, 0.042), (26, 0.009), (27, 0.019), (28, -0.055), (29, -0.015), (30, 0.023), (31, -0.051), (32, 0.014), (33, 0.06), (34, 0.004), (35, 0.047), (36, 0.057), (37, 0.004), (38, -0.009), (39, -0.064), (40, 0.025), (41, 0.006), (42, 0.04), (43, -0.08), (44, 0.007), (45, 0.008), (46, 0.046), (47, -0.058), (48, -0.022), (49, 0.093)]

similar blogs list:

simIndex simValue blogId blogTitle

same-blog 1 0.96176779 941 high scalability-2010-11-15-How Google's Instant Previews Reduces HTTP Requests

Introduction: In a strange case of synchronicity, Google just published Instant Previews: Under the hood , a very well written blog post by Matías Pelenur of the Instant Previews team, giving some fascinating inside details on how Google implemented Instant Previews . It's syncronicty because I had just posted  Strategy: Biggest Performance Impact Is To Reduce The Number Of HTTP Requests  and one of the major ideas behind the design Instant Previews is to reduce the number of HTTP requests through a few well chosen tricks. Cosmic! Some of what Google does to reduce HTTP requests: Data URIs , which are are base64 encodings of image data, are used instead of static images that are served from the server. This means the whole preview can be pieced together from image slices in one request as both the data and the image are returned in the same request. Google found that even though base64 encoding adds about 33% to the size of the image, tests showed that gzip-compressed data URIs are compara

2 0.75024509 942 high scalability-2010-11-15-Strategy: Biggest Performance Impact is to Reduce the Number of HTTP Requests

Introduction: Low Cost, High Performance, Strong Security: Pick Any Three  by Chris Palmer has a funny and informative presentation where the main message is: reduce the size and frequency of network communications, which will make your pages load faster, which will improve performance enough that you can use HTTPS all the time, which will make you safe and secure on-line, which is a good thing . The benefits of HTTPS for security are overwhelming, but people are afraid of the performance hit. The argument is successfully made that the overhead of HTTPS is low enough that you can afford the cost if you do some basic optimization. Reducing the number of HTTP requests is a good source of low hanging fruit. From the Yahoo UI Blog : Reducing the number of HTTP requests has the biggest impact on reducing response time and is often the easiest performance improvement to make. From the Experience of Gmail :  …we found that there were between fourteen and twenty-four HTTP requests require

3 0.70860827 394 high scalability-2008-09-25-HighScalability.com Rated 16th Best Blog for Development Managers

Introduction: Jurgen Appelo of Noop.nl asked for nominations for top blogs and then performed a sophisticated weighting of their popularity based on page range, trust authority, Alexa rank, Google hits, and number of comments. When all the results poured out of the blender HighScalability was ranked 16th. Not bad! Joel on Software was number one, of course. The next few were: 2) Coding Horror by Jeff Atwood 3) Seth's Blog by Seth Godin and 4) Paul Graham: Essays Paul Graham. All excellent blogs. Very cool.

4 0.67377144 665 high scalability-2009-07-29-Strategy: Let Google and Yahoo Host Your Ajax Library - For Free

Introduction: Update: Offloading ALL JS Files To Google . Now you can let Google serve all your javascript files. This article tells you how to do it (upload to Google Code Project) and why it's a big win (cheap, fast, caching, parallel downloads, save bandwidth). Don't have a CDN? Why not let Google and Yahoo be your CDN? At least for Ajax libraries. No charge. Google runs a content distribution network and loading architecture for the most popular open source JavaScript libraries , which include: jQuery, prototype, script.aculo.us, MooTools, and dojo. The idea is web pages directly include your library of choice from Google's global, fast, and highly available network. Some have found much better performance and others experienced slower performance. My guess is the performance may be slower if your data center is close to you, but far away users will be much happier. Some negatives: not all libraries are included, you'll load more than you need because all functionality is included. Yahoo

5 0.66257471 242 high scalability-2008-02-07-Looking for good business examples of compaines using Hadoop

Introduction: I have read the blog about Mailtrust/Rackspace as well the interesting things with Google and Yahoo. Who else is using Hadoop/MapReduce to solve business problems. TIA johnmwillis.com

6 0.65480852 1143 high scalability-2011-11-16-Google+ Infrastructure Update - the JavaScript Story

7 0.61680996 981 high scalability-2011-02-01-Google Strategy: Tree Distribution of Requests and Responses

8 0.6135298 1275 high scalability-2012-07-02-C is for Compute - Google Compute Engine (GCE)

9 0.61222774 946 high scalability-2010-11-22-Strategy: Google Sends Canary Requests into the Data Mine

10 0.60875589 286 high scalability-2008-03-20-Paper: Asynchronous HTTP and Comet architectures

11 0.60852933 1266 high scalability-2012-06-18-Google on Latency Tolerant Systems: Making a Predictable Whole Out of Unpredictable Parts

12 0.59865767 1615 high scalability-2014-03-19-Strategy: Three Techniques to Survive Traffic Surges by Quickly Scaling Your Site

13 0.59553879 1107 high scalability-2011-08-29-The Three Ages of Google - Batch, Warehouse, Instant

14 0.59196198 640 high scalability-2009-06-28-Google Voice Architecture

15 0.58450097 1078 high scalability-2011-07-12-Google+ is Built Using Tools You Can Use Too: Closure, Java Servlets, JavaScript, BigTable, Colossus, Quick Turnaround

16 0.58402508 301 high scalability-2008-04-08-Google AppEngine - A First Look

17 0.58300948 409 high scalability-2008-10-13-Challenges from large scale computing at Google

18 0.58190626 273 high scalability-2008-03-09-Best Practices for Speeding Up Your Web Site

19 0.57693237 1207 high scalability-2012-03-12-Google: Taming the Long Latency Tail - When More Machines Equals Worse Results

20 0.5669747 1533 high scalability-2013-10-16-Interview With Google's Ilya Grigorik On His New Book: High Performance Browser Networking


similar blogs computed by lda model

lda for this blog:

topicId topicWeight

[(1, 0.043), (2, 0.161), (56, 0.48), (61, 0.075), (79, 0.108)]

similar blogs list:

simIndex simValue blogId blogTitle

1 0.94743401 1394 high scalability-2013-01-25-Stuff The Internet Says On Scalability For January 25, 2013

Introduction: Sorry, Stuff the Internet Says has been called on the account of a power outage. Gods of rain and tree have interfered with thee. Instead, how about watching a little Python? (that's Monty, not the language)

2 0.77792662 779 high scalability-2010-02-16-Seven Signs You May Need a NoSQL Database

Introduction: While exploring deep into some dusty old library stacks, I dug up Nostradamus' long lost NoSQL codex. What are the chances? Strangely, it also gave the plot to the next Dan Brown novel, but I left that out for reasons of sanity. About NoSQL, here is what Nosty (his friends call him Nosty) predicted are the signs you may need a NoSQL database... You noticed a lot of your database fields are really serialized complex objects in disguise . Why bother with a RDBMS at all then? Storing serialized objects in a relational database is like being on the pill while trying to get pregnant, a bit counter productive. Just use a schemaless database from the start. Using a standard query language has become too confining . You just want to be free. SQL is so easy, so convenient, and so standard, it's really not a challenge anymore. You need to be different. Then NoSQL is for you. Each has their own completely different query mechanism . Your toolbox only contains a hammer . Hammers wh

3 0.77490014 1022 high scalability-2011-04-13-Paper: NoSQL Databases - NoSQL Introduction and Overview

Introduction: Christof Strauch, from Stuttgart Media University, has written an incredible 120+ page paper titled NoSQL Databases  as an introduction and overview to NoSQL databases . The paper was written between 2010-06 and 2011-02, so it may be a bit out of date, but if you are looking to take in the NoSQL world in one big gulp, this is your chance. I asked Christof to give us a  short taste of what he was trying to accomplish in his paper: The paper aims at giving a systematic and thorough introduction and overview of the NoSQL field by assembling information dispersed among blogs, wikis and scientific papers. It firstly discusses reasons, rationales and motives for the development and usage of nonrelational database systems. These can be summarized by the need for high scalability, the processing of large amounts of data, the ability to distribute data among many (often commodity) servers, consequently a distribution-aware design of DBMSs. The paper then introduces fundamental concepts,

4 0.75793725 45 high scalability-2007-07-30-Product: SmarterStats

Introduction: SmarterStats provides a solid architecture businesses and individual end users can use to track growth and forecast internet trends. * Track your website's growth and forecast internet trends * Features over 130 report items, plus Geographic Reporting * Log comparison saving 90% of your disk space * Email Reports available in Enterprise Edition * Enhanced data mining available in both editions

same-blog 5 0.74206352 941 high scalability-2010-11-15-How Google's Instant Previews Reduces HTTP Requests

Introduction: In a strange case of synchronicity, Google just published Instant Previews: Under the hood , a very well written blog post by Matías Pelenur of the Instant Previews team, giving some fascinating inside details on how Google implemented Instant Previews . It's syncronicty because I had just posted  Strategy: Biggest Performance Impact Is To Reduce The Number Of HTTP Requests  and one of the major ideas behind the design Instant Previews is to reduce the number of HTTP requests through a few well chosen tricks. Cosmic! Some of what Google does to reduce HTTP requests: Data URIs , which are are base64 encodings of image data, are used instead of static images that are served from the server. This means the whole preview can be pieced together from image slices in one request as both the data and the image are returned in the same request. Google found that even though base64 encoding adds about 33% to the size of the image, tests showed that gzip-compressed data URIs are compara

6 0.72345269 732 high scalability-2009-10-29-Digg - Looking to the Future with Cassandra

7 0.66831905 446 high scalability-2008-11-18-Scalability Perspectives #2: Van Jacobson – Content-Centric Networking

8 0.65159082 854 high scalability-2010-07-09-Hot Scalability Links for July 9, 2010

9 0.65132469 759 high scalability-2010-01-11-Strategy: Don't Use Polling for Real-time Feeds

10 0.65113509 67 high scalability-2007-08-17-What is the best hosting option?

11 0.59225869 659 high scalability-2009-07-20-A Scalability Lament

12 0.56736398 815 high scalability-2010-04-27-Paper: Dapper, Google's Large-Scale Distributed Systems Tracing Infrastructure

13 0.55989718 1322 high scalability-2012-09-14-Stuff The Internet Says On Scalability For September 14, 2012

14 0.55001682 479 high scalability-2008-12-29-Platform virtualization - top 25 providers (software, hardware, combined)

15 0.48193553 245 high scalability-2008-02-12-Product: rPath - Creating and Managing Virtual Appliances

16 0.47480255 1565 high scalability-2013-12-16-22 Recommendations for Building Effective High Traffic Web Software

17 0.45042109 981 high scalability-2011-02-01-Google Strategy: Tree Distribution of Requests and Responses

18 0.44520235 744 high scalability-2009-11-24-Hot Scalability Links for Nov 24 2009

19 0.43992716 487 high scalability-2009-01-08-Paper: Sharding with Oracle Database

20 0.43873993 1183 high scalability-2012-01-30-37signals Still Happily Scaling on Moore RAM and SSDs