Library Hours
Monday to Friday: 9 a.m. to 9 p.m.
Saturday: 9 a.m. to 5 p.m.
Sunday: 1 p.m. to 9 p.m.
Naper Blvd. 1 p.m. to 5 p.m.
LEADER 00000cam a2200613 i 4500
003 OCoLC
005 20240129213017.0
006 m o d
007 cr unu||||||||
008 171017s2017 caua ob 001 0 eng d
019 1004758619|a1005003528|a1103280677|a1202557229|a1240509401
020 9781491951521
020 1491951524
029 1 GBVCP|b1014936411
035 (OCoLC)1006510694|z(OCoLC)1004758619|z(OCoLC)1005003528
|z(OCoLC)1103280677|z(OCoLC)1202557229|z(OCoLC)1240509401
037 CL0500000902|bSafari Books Online
040 UMI|beng|erda|epn|cUMI|dOCLCF|dSTF|dCEF|dKSU|dUAB|dEBLCP
|dYDX|dVT2|dOCLCQ|dOCLCO|dOCLCQ|dOCLCO
049 INap
082 04 004.24
082 04 004.24|223
099 eBook O'Reilly for Public Libraries
100 1 Kejariwal, Arun,|eauthor.
245 14 The art of capacity planning :|bscaling web resources in
the cloud /|cArun Kejariwal and John Allspaw.|h[O'Reilly
electronic resource]
250 Second edition.
264 1 Sebastopol, CA :|bO'Reilly Media,|c2017.
300 1 online resource (1 volume) :|billustrations
336 text|btxt|2rdacontent
337 computer|bc|2rdamedia
338 online resource|bcr|2rdacarrier
500 Previous edition published: 2008.
504 Includes bibliographical references and index.
505 0 Copyright; Table of Contents; Preface; Why We Wrote and
Revised This Book; Focus and Topics; Audience for This
Book; Organization of the Material; Conventions Used in
This Book; O'Reilly Safari; Using Code Examples; We'd Like
to Hear from You; Acknowledgments; Chapter 1. Goals,
Issues, and Processes in Capacity Planning; Background;
Preliminaries; Quick and Dirty Math; Predicting When
Systems Will Fail; Make System Stats Tell Stories; Buying
Stuff; Performance and Capacity: Two Different Animals;
The Effects of Social Websites and Open APIs; Readings;
Critical Section; Resources.
505 8 Chapter 2. Setting Goals for CapacityDifferent Kinds of
Requirements and Measurements; External Service
Monitoring; SLAs; Business Capacity Requirements; User
Expectations; Architecture Decisions; Providing
Measurement Points; Resource Ceilings; Hardware Decisions
(Vertical, Horizontal, and Diagonal Scaling); Disaster
Recovery; Readings; Resources; Chapter 3. Measurement:
Units of Capacity; Capacity Tracking Tools; Fundamentals
and Elements of Metric Collection Systems; Round-Robin
Database and RRDTool; Ganglia; Simple Network Management
Protocol; Treating Logs as Past Metrics.
505 8 Monitoring as a Tool for Urgent Problem
IdentificationNetwork Measurement and Planning; Load
Balancing; Applications of Monitoring; Application-Level
Measurement; Storage Capacity; Database Capacity; Caching
Systems; Establishing Caching System Ceilings; Special Use
and Multiple Use Servers; API Usage and Its Effect on
Capacity; Examples and Reality; Summary; Readings;
Performance; Network; Load Balancer; Storage; Database and
Caching; Resources; Chapter 4. Predicting Trends; Riding
the Waves; Trends, Curves, and Time; Tying Application
Level Metrics to System Statistics: Database Example.
505 8 Forecasting Peak-Driven Resource Usage: Web Server
ExampleCaveats Concerning Small Datasets; Automating the
Forecasting; Safety Factors; Procurement; Procurement Time
: The Killer Metric; Just-in-Time Inventory; The Effects
of Increasing Capacity; Long-Term Trends; Traffic Pattern
Changes; Application Usage Changes and Product Planning;
Iteration and Calibration; Best Guesses; Diagonal Scaling
Opportunities; Summary; Readings; Buy or Lease; Time-
Series Forecasting; Curve Fitting; Measurement; Resources;
Chapter 5. Deployment; Automated Deployment Philosophies.
505 8 Goal 1: Minimize Time to Provision New CapacityGoal 2: All
Changes Happen in One Place; Goal 3: Never Log in to an
Individual Server (for Management); Goal 4: Have New
Servers Start Working Automatically; Goal 5: Maintain
Consistency for Easier Troubleshooting; Automated
Installation Tools; Preparing the OS Image; The
Installation Process; Automated Configuration; Defining
Roles and Services; An Example: Splitting Off Static Web
Content; User Management and Access Control; Ad Hockery;
Example 2: Multiple Datacenters; Summary; Readings;
Resources; Chapter 6. Autoscaling; The Challenge.
520 In their early days, Twitter, Flickr, Etsy, and many other
companies experienced sudden spikes in activity that took
their web services down in minutes. Today, determining how
much capacity you need for handling traffic surges is
still a common frustration of operations engineers and
software developers. This hands-on guide provides the
knowledge and tools you need to measure, deploy, and
manage your web application infrastructure before you
experience explosive growth--|cSource other than Library
of Congress.
588 0 Online resource; title from title page (Safari, viewed
October 13, 2017).
590 O'Reilly|bO'Reilly Online Learning: Academic/Public
Library Edition
650 0 Computer capacity|xPlanning.
650 0 Computer capacity|xManagement.
650 0 Web sites|xDesign.
650 6 Capacité de traitement|xPlanification.
650 6 Capacité de traitement|xGestion.
650 6 Sites Web|xConception.
650 7 Computer capacity|xManagement|2fast
650 7 Computer capacity|xPlanning|2fast
650 7 Web sites|xDesign|2fast
700 1 Allspaw, John,|eauthor.
776 08 |iPrint version:|aKejariwal, Arun.|tArt of Capacity
Planning : Scaling Web Resources in the Cloud.|dSebastopol
: O'Reilly Media, Incorporated, ©2017|z9781491939208
856 40 |uhttps://ezproxy.naperville-lib.org/login?url=https://
learning.oreilly.com/library/view/~/9781491939192/?ar
|zAvailable on O'Reilly for Public Libraries
938 ProQuest Ebook Central|bEBLB|nEBL5057680
938 YBP Library Services|bYANK|n14814621
994 92|bJFN