| 商家名称 |
信用等级 |
购买信息 |
订购本书 |
|
|
 |
容量规划的艺术(影印版) |
 |
|
|
容量规划的艺术(影印版) |
|
基本信息·出版社：东南大学出版社
·页码：135 页
·出版日期：2009年08月
·ISBN：7564116528/9787564116521
·条形码：9787564116521
·版本：第1版
·装帧：平装
·开本：16
·正文语种：英语
·外文书名：The Art of Capacity Planning
内容简介 《容量规划的艺术(影印版)》作者JohnAllspaw是图片共享网站Flickr.com的运营工程经理。使用和发展情况用于衡量Web的成功与否，而基于Web的公司生存与否取决于他们根据不断增长的需求扩展基础架构的能力。这本简单实用的指南将给予你需要用来测量、部署和管理w曲应用程序架构的知识和工具，以走在具有威胁的瓶颈和急速的增长前面。《容量规划的艺术》汲取了Flickr的成长中很多作者的个人心得，并结合了作者在其他企业工作的同仁们的领悟。他们的第一手经验将会是你测算增长、预测趋势和做出符合成本效益的准备工作的有力方针。主题包括： 使用高效的工具用于测量及部署存储、数据库和应用服务能力的分析和预测设计易于添加并测算其效能的架构处理突发流量峰值预测指数式和爆发式增长使虚拟化和像EC2这样的云服务与容量策略相适应在本书中，作者Allspaw利用多年的宝贵经验，从Flickr的早期，当他不得不去管理任何具有成长型互动状态服务（web presence）的公司典型的成本与性能的平衡开始讲述。他在《容量规划的艺术》中给出的建议将会帮助你为突发的增长做好准备，对你会有非常大的帮助。
作者简介 John Allspaw is currently the operations engineering manager at Flickr.com, the popular photo-sharing site. He has had extensive experience working with growing websites since 1999. These include online news magazines (Salon.corn, InfoWorld.com,Macworld.corn) and social networking sites that have experienced extreme growth(Friendster and Flickr).
During John's time at Friendster, traffic increased fivefold. He was responsible for Friend-ster's transition from a couple dozen servers in a failing data center to more than 400 machines across two data centers, and the complete redesign of the backing infrastructure.When he joined Flickr, it had 10 servers in a tiny data center in Vancouver; it is nowlocated in multiple data centers across the U.S.
Prior to his web experience, John worked in modeling and simulation as a mechanical engineer performing car crash simulations for the NHTSA.
媒体推荐 “John AIIspaw的书在入门时非常有用——非常实用的Web工作原理深入研究。无论你是正在团队中学习采购过程（procurement process），还是必须成功计划一些详细而明确的方法，这本书对于任何想了解如何构建下一个Flickr的人都是必读教材。”
——Chad Dickerson，Etsy网站的CTO，Salon．com和InfoWorld．com的前任CTO，以及Yahoo！Developer Network和Brickhouse的主管
编辑推荐 《容量规划的艺术(影印版)》由东南大学出版社出版。
目录 PREFACE
1 GOALS, ISSUES, AND PROCESSES IN CAPACITY PLANNING
Quick and Dirty Math
PredictinR When Your Systems Will Fail
Make Your System Stats Tell Stories
BuyinR Stuff: Procurement Is a Process
Performance and Capacity: Two Different Animals
The Effects of Social Websites and Open APIs
2 SETTING GOALS FOR CAPACITY
Different Kinds of Requirements and Measurements
Architecture Decisions
3 MEASUREMENT: UNITS OF CAPACITY
Aspects of Capacity Tracking Tools
Applications of MonitorinR
API UsaRe and Its Effect on Capacity
Examples and Reality
Summary
4 PREDICTING TRENDS
RidinR Your Waues
Procurement
The Effects of Increasing Capacity
LonR-Term Trends
Iteration and Calibration
Summary
5 DEPLOYMENT
Automated Deployment Philosophies
Automated Installation Tools
Automated ConfiRuration
Summary
A VIRTUALIZATION AND CLOUD COMPUTING
B DEALING WITH INSTANTANEOUS GROWTH
C CAPACITY TOOLS
INDEX
……
文摘 插图：
Databases are complex beasts，and finding the limits of your database can be time consum.ing，but well worth the effort.Just as with web servers，database capadty tends to bepeak.driven.meaning their limits are usually defined by how they perform during theheaviest periods of end.user activity.As a result.we generally take a close look at the peaktraffic times to see what’s going on with system resources.and take it from there.But before we start hunting for the magical‘red line’of database consumption；remem.ber.I recommend looking at how your database performs with real queries and real data.One of the first things you should determine is when your database is expected to run outof hardware resources.relative to traffic.Depending on the load characteristics.you mightbe bound by the CPU，the network，or disk I／O.If you are lucky enough to keep your most.requested data in memory.you might findyourself being constrained by CPU or network resources.This situation makes your huntfor a performance ceiling a bit easier as you need only track a single number，as we discov.ered when monitoring Apache performance.
