DOCSLIB.ORG

Parallelizing the Web Browser

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Parallelizing the Web Browser Parallelizing the Web Browser Christopher Grant Jones, Rose Liu, Leo Meyerovich, Krste Asanovic,´ Rastislav Bodík Department of Computer Science, University of California, Berkeley {cgjones,rfl,lmeyerov,krste,bodik}@cs.berkeley.edu Abstract load time is still slowed down by 50%. On an equiva- lent network connection, the iPhone browser is 5 to 10- We argue that the transition from laptops to handheld times slower than Firefox on a fast laptop. The browser computers will happen only if we rethink the design of is CPU-bound because it is a compiler (for HTML), a web browsers. Web browsers are an indispensable part page layout engine (for CSS), and an interpreter (for of the end-user software stack but they are too ineffi- JavaScript); all three tasks are on a user’s critical path. cient for handhelds. While the laptop reused the soft- The successively smaller form factors of previous ware stack of its desktop ancestor, solid-state device computer generations (workstations, desktops, and then trends suggest that today’s browser designs will not be- laptops) were enabled by exponential improvements in come sufficiently (1) responsive and (2) energy-efficient. the performance of single-thread execution. Future We argue that browser improvements must go beyond CMOS generations are expected to increase the clock JavaScript JIT compilation and discuss how parallelism frequency only marginally, and handheld application de- may help achieve these two goals. Motivated by a future velopers have already adapted to the new reality: rather browser-based application, we describe the preliminary than developing their applications in the browser, as is design of our parallel browser, its work-efficient parallel the case on the laptop, they rely on native frameworks algorithms, and an actor-based scripting language. such as the iPhone SDK (Objective C), Android (Java), or Symbian (C++). These frameworks offer higher per- 1 Browsers on Handheld Computers formance but do so at the cost of portability and pro- Bell’s Law of Computer Classes predicts that handheld grammer productivity. computers will soon replace and exceed laptops. Indeed, 2 An Efficient Web Browser internet-enabled phones have already eclipsed laptops in number, and may soon do so in input-output capability We want to redesign browsers in order to improve their as well. The first phone with a pico-projector (Epoq) (1) responsiveness and (2) energy efficiency. While our launched in 2008; wearable and foldable displays are primary motivation is the handheld browser, most im- in prototyping phases. Touch screens keyboards and provements will benefit laptop browsers equally. There speech recognition have become widely adopted. Con- are several ways to achieve the two goals: tinuing Bell’s prediction, phone sensors may enable ap- • Offloading the computation. Used in the Deepfish plications not feasible on laptops. and Skyfire mobile browsers, a server-side proxy Further evolution of handheld devices is limited browser renders a page and sends compressed im- mainly by their computing power. Constrained by the ages to a handheld. Offloading bulk computations, battery and heat dissipation, the mobile CPU noticeably such as speech recognition, seems attractive, but impacts the web browser in particular: even with a fast adding server latencies exceeds the 40ms threshold wi-fi connection, the iPhone may take 20 seconds to load for visual perception, making proxy architectures the Slashdot home page. Until mobile browsers become insufficient for interactive GUIs. Disconnected op- dramatically more responsive, they will continue to be eration is inherently impossible. used only when a laptop browser is not available. With- • Removing the abstraction tax. Browser program- out a fast browser, handhelds may not be able to support mers pay for their increased productivity with an compelling web applications, such as Google Docs, that abstraction tax—the overheads of the page layout are sprouting in laptop browsers. engine, the JavaScript interpreter, parsers for ap- One may expect that mobile browsers are network- plications deployed in plain text, and other com- bound, but this is not the case. On a 2Mbps network ponents. We measured this tax to be two orders of connection, soon expected on internet phones, the CPU magnitude: a small Google Map JavaScript appli- bottleneck becomes visible: On a ThinkPad X61 lap- cation runs about 70-times slower than the equiv- top, halving the CPU frequency doubles the Firefox page alent written using C and pixel frame buffers [3]. load times for cached pages; with a cold cache, the Removing the abstraction tax is attractive because it improves both responsiveness (the program runs What are the implications of these trends on browser faster) and energy efficiency (the program performs parallelization? Consider the goal of sustained 50-way less work). JavaScript overheads can be reduced parallelization execution. A pertinent question is how with JIT compilation, typically 5 to 10-times, but much of the browser we can afford not to parallelize. browsers often spend only 15% of time in the inter- Assume that the processor can execute 250 parallel op- preter. Abstraction reduction remains attractive but erations. Amdahl’s Law shows that to to sustain 50-way we leave it out of this paper. parallelism, only 4% of the browser execution can re- • Parallelizing the browser. Future CMOS genera- main sequential, with the rest running at 250-way paral- tions will not allow significantly faster clock rates, lelism. Obtaining this level of parallelism is challenging but they will be about 25% more energy efficient because, with the exception of media decoding, browser per generation. The savings translate into addi- algorithms have been optimized for single-threaded ex- tional cores, already observed in handhelds. Paral- ecution. This paper suggests that it may be possible to lelizing the browser improves responsiveness (goal uncover 250-way parallelism in the browser. 1) and to some extent also energy efficiency (goal 2. Type of parallelism: Should we exploit task paral- 2): vector instructions improve energy efficiency lelism, data parallelism, or both? Data parallel architec- per operation, and although parallelization does not tures such as SIMD are efficient because their instruc- decrease the amount of work, gains in program ac- tion delivery, which consumes about 50% of energy on celeration may allow us to slow down the clock, superscalar processors, is amortized among the parallel further improving the energy efficiency. operations. A vector accelerator has been shown to in- The rest of this paper discusses how one may go about crease energy efficiency 10-times [9]. In this paper, we parallelizing the web browser. show that at least a part of the browser can be imple- mented in data parallel fashion. 3 What Kind of Parallelism? 3. Algorithms: Which parallel algorithms improve en- The performance of the browser is ultimately limited by ergy efficiency? Parallel algorithms that accelerate pro- energy constraints and these constraints dictate optimal grams do not necessarily improve energy efficiency. parallelization strategies. Ideally, we want to minimize The handheld calls for parallel algorithms that are work energy consumption while being sufficiently responsive. efficient—i.e., they do not perform more total work than This goal motivates the following questions: a sequential algorithm. An example of a work-inefficient 1. Amount of parallelism: Do we decompose the algorithm is speculative parallelization that misspecu- browser into 10 or 1000 parallel computations? The lates too often. Work efficiency is a demanding re- answer depends primarily on the parallelism available in quirement: for some “inherently sequential” problems, handheld processors. In five years, 1W processors are such as finite-state machines, only work-inefficient al- expected to have about four cores. With two threads per gorithms are known [5]. We show that careful specula- core and 8-wide SIMD instructions, devices may thus tion allows work-efficient parallelization of finite state support about 64-way parallelism. machines in the lexical analysis. The second consideration comes from voltage scal- ing. The energy efficiency of CMOS transistors in- 4 The Browser Anatomy creases when the frequency and supply voltage are de- Original web browsers were designed to render hyper- creased; parallelism accelerates the program to make up linked documents. Later, JavaScript programs, embed- for the lower frequency. How much more parallelism ded in the document, provided simple animated menus can we get? There is a limit to CMOS scaling benefits: by dynamically modifying the document. Today, AJAX reducing clock frequency beyond roughly 3-times from applications rival their desktop counterparts. the peak frequency no longer improves efficiency lin- The typical browser architecture is shown in Figure 1. early [6]. In the 65nm Intel Tera-scale processor, reduc- Loading an HTML page sets off a cascade of events: ing the frequency from 4Ghz to 1GHz reduces the en- The page is scanned, parsed, and compiled into a doc- ergy per operation 4-times, while for the ARM9, reduc- ument object model (DOM), an abstract syntax tree of ing supply voltage to near-threshold levels and running the document. Content referenced by URLs is fetched on 16 cores, rather on one, reduces energy consumption and inlined into the DOM. As the content necessary to by 5-times [15]. It might be possible to design mobile display the page becomes available, the page layout is processors that operate at the peak frequency allowed (incrementally) solved and drawn to the screen. After by the CMOS technology in short bursts (for example, the initial page load, scripts respond to events generated 10ms needed to layout a web page), scaling down the by user input and server messages, typically modifying frequency for the remainder of the execution; the scal- the DOM. This may, in turn, cause the page layout to be ing may allow them to exploit additional parallelism. recomputed and redrawn. optimized with sequential execution in mind.
Load more

Recommended publications
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • The Art, Science, and Engineering of Fuzzing: a Survey
    1 The Art, Science, and Engineering of Fuzzing: A Survey Valentin J.M. Manes,` HyungSeok Han, Choongwoo Han, Sang Kil Cha, Manuel Egele, Edward J. Schwartz, and Maverick Woo Abstract—Among the many software vulnerability discovery techniques available today, fuzzing has remained highly popular due to its conceptual simplicity, its low barrier to deployment, and its vast amount of empirical evidence in discovering real-world software vulnerabilities. At a high level, fuzzing refers to a process of repeatedly running a program with generated inputs that may be syntactically or semantically malformed. While researchers and practitioners alike have invested a large and diverse effort towards improving fuzzing in recent years, this surge of work has also made it difficult to gain a comprehensive and coherent view of fuzzing. To help preserve and bring coherence to the vast literature of fuzzing, this paper presents a unified, general-purpose model of fuzzing together with a taxonomy of the current fuzzing literature. We methodically explore the design decisions at every stage of our model fuzzer by surveying the related literature and innovations in the art, science, and engineering that make modern-day fuzzers effective. Index Terms—software security, automated software testing, fuzzing. ✦ 1 INTRODUCTION Figure 1 on p. 5) and an increasing number of fuzzing Ever since its introduction in the early 1990s [152], fuzzing studies appear at major security conferences (e.g. [225], has remained one of the most widely-deployed techniques [52], [37], [176], [83], [239]). In addition, the blogosphere is to discover software security vulnerabilities. At a high level, filled with many success stories of fuzzing, some of which fuzzing refers to a process of repeatedly running a program also contain what we consider to be gems that warrant a with generated inputs that may be syntactically or seman- permanent place in the literature.
    [Show full text]
  • Freedom: Engineering a State-Of-The-Art DOM Fuzzer
    FreeDom: Engineering a State-of-the-Art DOM Fuzzer Wen Xu Soyeon Park Taesoo Kim Georgia Institute of Technology Georgia Institute of Technology Georgia Institute of Technology [email protected] [email protected] [email protected] ABSTRACT ACM Reference Format: The DOM engine of a web browser is a popular attack surface and Wen Xu, Soyeon Park, and Taesoo Kim. 2020. FreeDom: Engineering a State- has been thoroughly fuzzed during its development. A common of-the-Art DOM Fuzzer. In Proceedings of the 2020 ACM SIGSAC Conference on Computer and Communications Security (CCS ’20), November 9–13, 2020, approach adopted by the latest DOM fuzzers is to generate new Virtual Event, USA. ACM, New York, NY, USA, 16 pages. https://doi.org/10. inputs based on context-free grammars. However, such a generative 1145/3372297.3423340 approach fails to capture the data dependencies in the inputs of a DOM engine, namely, HTML documents. Meanwhile, it is unclear whether or not coverage-guided mutation, which is well-known to 1 INTRODUCTION be effective in fuzzing numerous software, still remains to beeffec- A DOM (Document Object Model) engine is a core component of tive against DOM engines. Worse yet, existing DOM fuzzers cannot every modern web browser, which is responsible for displaying adopt a coverage-guided approach because they are unable to fully HTML documents in an interactive window on an end-user device. support HTML mutation and suffer from low browser throughput. Considering its giant code base and extraordinary complexity, a To scientifically understand the effectiveness and limitations of DOM engine has always been one of the largest bug sources in a web the two approaches, we propose FreeDom, a full-fledged cluster- browser.
    [Show full text]
  • RSA Adaptive Authentication
    RSA Adaptive Authentication (Hosted) Data Gathering Techniques Guide Contact Information Go to the RSA corporate web site for regional Customer Support telephone and fax numbers: www.rsa.com Trademarks RSA, the RSA Logo and EMC are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. All other trademarks used herein are the property of their respective owners. For a list of RSA trademarks, go to www.rsa.com/legal/trademarks_list.pdf. License agreement This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any other person. No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability. This software is subject to change without notice and should not be construed as a commitment by EMC. Note on encryption technologies This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when using, importing or exporting this product. Distribution Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC believes the information in this publication is accurate as of its publication date.
    [Show full text]
  • Appendix a the Ten Commandments for Websites
    Appendix A The Ten Commandments for Websites Welcome to the appendixes! At this stage in your learning, you should have all the basic skills you require to build a high-quality website with insightful consideration given to aspects such as accessibility, search engine optimization, usability, and all the other concepts that web designers and developers think about on a daily basis. Hopefully with all the different elements covered in this book, you now have a solid understanding as to what goes into building a website (much more than code!). The main thing you should take from this book is that you don’t need to be an expert at everything but ensuring that you take the time to notice what’s out there and deciding what will best help your site are among the most important elements of the process. As you leave this book and go on to updating your website over time and perhaps learning new skills, always remember to be brave, take risks (through trial and error), and never feel that things are getting too hard. If you choose to learn skills that were only briefly mentioned in this book, like scripting, or to get involved in using content management systems and web software, go at a pace that you feel comfortable with. With that in mind, let’s go over the 10 most important messages I would personally recommend. After that, I’ll give you some useful resources like important websites for people learning to create for the Internet and handy software. Advice is something many professional designers and developers give out in spades after learning some harsh lessons from what their own bitter experiences.
    [Show full text]
  • Skyfire: Data-Driven Seed Generation for Fuzzing
    Skyfire: Data-Driven Seed Generation for Fuzzing Junjie Wang, Bihuan Chen†, Lei Wei, and Yang Liu Nanyang Technological University, Singapore {wang1043, bhchen, l.wei, yangliu}@ntu.edu.sg †Corresponding Author Abstract—Programs that take highly-structured files as inputs Syntax Semantic normally process inputs in stages: syntax parsing, semantic check- Features Rules ing, and application execution. Deep bugs are often hidden in the <?xml version="1.0" application execution stage, and it is non-trivial to automatically encoding="utf- pass pass pass 8"?><xsl:stylesheet version="1.0" Syntax Semantic Application xmlns:xsl="http://www.w3 .org/1999/XSL/Transform" generate test inputs to trigger them. Mutation-based fuzzing gen- ><xsl:output xsl:use- √ attribute- Parsing Checking Execution erates test inputs by modifying well-formed seed inputs randomly sets=""/></xsl:stylesheet> Parsing Semantic or heuristically. Most inputs are rejected at the early syntax pars- Inputs Crashes ing stage. Differently, generation-based fuzzing generates inputs Errors Violations from a specification (e.g., grammar). They can quickly carry the ! ! X fuzzing beyond the syntax parsing stage. However, most inputs fail to pass the semantic checking (e.g., violating semantic rules), Fig. 1: Stages of Processing Highly-Structured Inputs which restricts their capability of discovering deep bugs. In this paper, we propose a novel data-driven seed generation approach, named Skyfire, which leverages the knowledge in the analysis [8, 9] that identifies those interesting bytes to mutate, vast amount of existing samples to generate well-distributed seed symbolic execution [10, 11, 12] that relies on constraint solving inputs for fuzzing programs that process highly-structured inputs.
    [Show full text]
  • 0789747189.Pdf
    Mark Bell 800 East 96th Street, Indianapolis, Indiana 46240 Build a Website for Free Associate Publisher Copyright © 2011 by Pearson Education Greg Wiegand All rights reserved. No part of this book shall be Acquisitions Editor reproduced, stored in a retrieval system, or transmit- Laura Norman ted by any means, electronic, mechanical, photo- copying, recording, or otherwise, without written Development Editor permission from the publisher. No patent liability is Lora Baughey assumed with respect to the use of the information contained herein. Although every precaution has Managing Editor been taken in the preparation of this book, the Kristy Hart publisher and author assume no responsibility for Senior Project Editor errors or omissions. Nor is any liability assumed for Betsy Harris damages resulting from the use of the information contained herein. Copy Editor ISBN-13: 978-0-7897-4718-1 Karen A. Gill ISBN-10: 0-7897-4718-9 Indexer The Library of Congress Cataloging-in-Publication Erika Millen data is on file. Proofreader Williams Woods Publishing Services Technical Editor Christian Kenyeres Publishing Coordinator Cindy Teeters Book Designer Anne Jones Compositor Nonie Ratcliff Trademarks All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Que Publishing cannot attest to the accuracy of this infor- mation. Use of a term in this book should not be regarded as affecting the validity of any trademark or service mark. Warning and Disclaimer Every effort has been made to make this book as complete and as accurate as possible, but no warranty or fitness is implied. The information provided is on an “as is” basis.
    [Show full text]
  • European Technology Media & Telecommunications Monitor
    European Technology Media & Telecommunications Monitor Market and Industry Update H1 2013 Piper Jaffray European TMT Team: Eric Sanschagrin Managing Director Head of European TMT [email protected] +44 (0) 207 796 8420 Jessica Harneyford Associate [email protected] +44 (0) 207 796 8416 Peter Shin Analyst [email protected] +44 (0) 207 796 8444 Julie Wright Executive Assistant [email protected] +44 (0) 207 796 8427 TECHNOLOGY, MEDIA & TELECOMMUNICATIONS MONITOR Market and Industry Update Selected Piper Jaffray H1 2013 TMT Transactions TMT Investment Banking Transactions Date: June 2013 $47,500,000 Client: IPtronics A/S Transaction: Mellanox Technologies, Ltd. signed a definitive agreement to acquire IPtronics A/S from Creandum AB, Sunstone Capital A/S and others for $47.5 million in cash. Pursuant to the Has Been Acquired By transaction, IPtronics’ current location in Roskilde, Denmark will serve as Mellanox’s first research and development centre in Europe and IPtronics A/S will operate as a wholly-owned indirect subsidiary of Mellanox Technologies, Ltd. Client Description: Mellanox Technologies Ltd. is a leading supplier of end-to-end InfiniBand and June 2013 Ethernet interconnect solutions and services for servers and storage. PJC Role: Piper Jaffray acted as exclusive financial advisor to IPtronics A/S. Date: May 2013 $46,000,000 Client: inContact, Inc. (NasdaqCM: SAAS) Transaction: inContact closed a $46.0 million follow-on offering of 6,396,389 shares of common stock, priced at $7.15 per share. Client Description: inContact, Inc. provides cloud contact center software solutions. PJC Role: Piper Jaffray acted as bookrunner for the offering.
    [Show full text]
  • Towards Automated Generation of Exploitation Primitives for Web
    Towards Automated Generation of Exploitation Primitives for Web Browsers Behrad Garmany Martin Stoffel Robert Gawlik Ruhr-Universität Bochum Ruhr-Universität Bochum Ruhr-Universität Bochum [email protected] [email protected] [email protected] Philipp Koppe Tim Blazytko Thorsten Holz Ruhr-Universität Bochum Ruhr-Universität Bochum Ruhr-Universität Bochum [email protected] [email protected] [email protected] ABSTRACT ACM Reference Format: The growing dependence on software and the increasing complexity Behrad Garmany, Martin Stoffel, Robert Gawlik, Philipp Koppe, Tim Blazytko, of such systems builds and feeds the attack surface for exploitable and Thorsten Holz. 2018. Towards Automated Generation of Exploitation Primitives for Web Browsers. In 2018 Annual Computer Security Applications vulnerabilities. Security researchers put up a lot of effort to de- Conference (ACSAC ’18), December 3–7, 2018, San Juan, PR, USA. ACM, New velop exploits and analyze existing exploits with the goal of staying York, NY, USA, 13 pages. https://doi.org/10.1145/3274694.3274723 ahead of the state-of-the-art in attacks and defenses. The urge for automated systems that operate at scale, speed and efficiency is 1 INTRODUCTION therefore undeniable. Given their complexity and large user base, Software vulnerabilities pose a severe threat in practice as they web browsers pose an attractive target. Due to various mitigation are the root cause behind many attacks we observe on the In- strategies, the exploitation of a browser vulnerability became a ternet on a daily basis. A few years ago, attackers shifted away time consuming, multi-step task: creating a working exploit even from server-side vulnerabilities to client-side vulnerabilities.
    [Show full text]
  • How Far Can Client-Only Solutions Go for Mobile Browser Speed?
    How Far Can Client-Only Solutions Go for Mobile Browser Speed? Technical Report TR1215-2011, Rice University and Texas Instruments 1Zhen Wang, 2Felix Xiaozhu Lin, 1,2Lin Zhong, and 3Mansoor Chishtie 1Dept. of ECE and 2Dept of CS, Rice University, Houston, TX 77005 3Texas Instruments, Dallas, TX ABSTRACT The technical goal of this work is to answer this question, with the help of an unprecedented dataset of web browsing data conti- Mobile browser is known to be slow because of the bottleneck in nuously collected from 24 iPhone users over one year, or LiveLab resource loading. Client-only solutions to improve resource load- traces [14]. In achieving our goal, we make four contributions. ing are attractive because they are immediately deployable, scala- Firstly, we study browsing behavior of smartphone users and the ble, and secure. We present the first publicly known treatment of web pages visited by them. We find that subresources needed for client-only solutions to understand how much they can improve rendering a web page can be much more predictable than which mobile browser speed without infrastructure support. Leveraging webpage a user will visit because subresources have much higher an unprecedented set of web usage data collected from 24 iPhone revisit rate and a lot of them are shared by webpages from the users continuously over one year, we examine the three funda- same site. mental, orthogonal approaches a client-only solution can take: caching, prefetching, and speculative loading, which is first pro- Secondly, we quantitatively evaluate two popular client-only ap- posed and studied in this work.
    [Show full text]
  • Flywheel: Google's Data Compression Proxy for the Mobile
    Flywheel: Google’s Data Compression Proxy for the Mobile Web Victor Agababov∗ Michael Buettner Victor Chudnovsky Mark Cogan Ben Greenstein Shane McDaniel Michael Piatek Colin Scott† Matt Welsh Bolian Yin Google, Inc. †UC Berkeley Abstract Although the number of sites that are tuned for mo- bile devices is growing, there is still a huge opportunity Mobile devices are increasingly the dominant Internet to save users money by compressing web content via a access technology. Nevertheless, high costs, data caps, proxy. This paper describes Flywheel, a proxy service and throttling are a source of widespread frustration, and integrated into Chrome for Android and iOS that com- a significant barrier to adoption in emerging markets. presses proxied web content by 58% on average (50% This paper presents Flywheel, an HTTP proxy service median across users). While proxy optimization is an that extends the life of mobile data plans by compress- old idea [15, 22, 29, 39, 41] and the optimizations we ap- ing responses in-flight between origin servers and client ply are known, we have gained insights by studying a browsers. Flywheel is integrated with the Chrome web modern workload for a service deployed at scale. We browser and reduces the size of proxied web pages by describe Flywheel from an operational and design per- 50% for a median user. We report measurement results spective, backed by usage data gained from several years from millions of users as well as experience gained dur- of deployment and millions of active users. ing three years of operating and evolving the production service at Google.
    [Show full text]
  • Web Standards Web Standards: Mastering HTML5, CSS3, and XML Gives You a Deep Understand- Ing of How Web Standards Can Be Applied to Improve Your Website
    BOOKS FOR PROFESSIONALS BY PROFESSIONALS® Sikos, Ph.D. RELATED Web Standards Web Standards: Mastering HTML5, CSS3, and XML gives you a deep understand- ing of how web standards can be applied to improve your website. You will also find solutions to some of the most common website problems. You will learn how to create fully standards-compliant websites and provide search engine-optimized Web documents with faster download times, accurate rendering, lower development costs, and easy maintenance. Web Standards: Mastering HTML5, CSS3, and XML describes how you can make the most of web standards, through technology discussions as well as practical sam- ple code. As a web developer, you’ll have seen problems with inconsistent appearance and behavior of the same site in different browsers. Web standards can and should be used to completely eliminate these problems. With Web Standards, you’ll learn how to: • Hand code valid markup, styles, and news feeds • Provide meaningful semantics and machine-readable metadata • Restrict markup to semantics and provide reliable layout • Achieve full standards compliance Web standardization is not a sacrifice! By using this book, we can create and maintain a better, well-formed Web for everyone. CSS3, and XML CSS3, Mastering HTML5, US $49.99 Shelve in Web Development/General User level: Intermediate–Advanced SOURCE CODE ONLINE www.apress.com For your convenience Apress has placed some of the front matter material after the index. Please use the Bookmarks and Contents at a Glance links to access them. Download from Wow! eBook <www.wowebook.com> Contents at a Glance About the Author................................................................................................
    [Show full text]