- Paperback: 720 pages
- Publisher: O'Reilly Media; 1 edition (January 11, 2002)
- Language: English
- ISBN-10: 1565924665
- ISBN-13: 978-1565924666
- Product Dimensions: 7 x 1.3 x 9.2 inches
- Shipping Weight: 2 pounds (View shipping rates and policies)
- Average Customer Review: 6 customer reviews
- Amazon Best Sellers Rank: #5,642,430 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ $3.99 shipping
+ Free Shipping
+ Free Shipping
Windows 2000 Performance Guide: Help for Administrators and Application Developers Paperback – January 11, 2002
An Amazon Book with Buzz: "Ghosted"
Seven perfect days. Then he disappeared. A love story with a secret at its heart. Learn more
The load your users place on your Windows 2000 servers may increase approximately linearly over time, but that's no guarantee that the servers' performance will degrade smoothly and predictably. Rather--and this is the crux of Windows 2000 Performance Guide--a modest increase in workload can often cause a significant, even catastrophic, decrease in overall performance. The reason: Servers are complex systems, with each of their parts dependent upon many others. Your job in optimizing Windows 2000 machines is to spot the critical thresholds (preferably in advance) and adjust your systems to stay clear of them. Mark Friedman and Odysseas Pentakalos have done a considerable amount of empirical research into the behavior of all major Windows 2000 subsystems (and make frequent, detailed reference to the research of others) and present their findings here. Their approach is somewhat academic (you can't accurately describe performance without some calculations and statistics, as well as some theoretical discussion of operating system design), but there's no question that this volume fits into the "blue" series of system administration books. Software engineers--particularly those engaged in designing highly scalable applications for Windows 2000--will get a lot from this title, as well.
For starters, the authors go into depth on what the traces available in Performance Monitor mean--valuable stuff for a system administrator who's unclear on what "Context switches / sec" and "Thread % User Time" (to cite one example) have to say about how efficiently available resources are being used. Most of the instruction comes in the form of laboratory narratives that describe symptoms, systematic observations (i.e., how Perfmon was used for diagnosis), and corrective adjustments. In most cases, the authors explain the relative merits of better hardware, parallel hardware, application tuning, and other alternative solutions, but leave it up to readers to best resolve their own systems' particular troubles. --David Wall
Topics covered: The subsystems of Microsoft Windows 2000, how they interact, and how they affect overall system performance under different applications. Performance Monitor is dealt with in depth, as are the performance characteristics of CPUs (single and parallel), memory and paging, disk access and caching, network access, and Internet services. Threads and their priorities are explained in easily understood detail.
About the Author
Mark Friedman began his career as a programmer for the DuPont Corporation in 1977 and has been in the computer field ever since. He has a master's degree in computer science from Temple University and is the founder and president of Demand Technology Software. He has written numerous technical articles, conducts training seminars in Windows performance, and publishes a monthly newsletter. Currently, he is working on the design and development of professional software tools for Windows performance management.
Odysseas Pentakalos has been an independent consultant for 10 years, dealing with performance modeling and tuning of computer systems, as well as object-oriented design and development. His clients have included major government agencies and corporations such as NASA, the Army Research Lab, Sun Microsystems, and Concert Communications. Odysseas received a Ph.D. in computer science from the University of Maryland. He has published papers on performance topics in conferences, journals, and commercial publications.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
A couple of things that I would have liked to have seen in the book are:
(1) More detailed descriptions of each metric in PerfMon, together with what constitutes a good value and what doesn't.
(2) Details about socket options - how to choose values and what the impact of changing them is.
All in all, very good.
The Windows 2000 Performance Guide is the definitive book on its subject. It contains critical information that is often very hard to find, and in some cases simply unavailable, on a wide range of topics. The authors provide in-depth knowledge on everything from disk hardware to arcane operating system issues. Because the source of performance problems is often unclear, the book's breadth of scope is absolutely essential. These days, most computer experts are narrowly focused: it's just too difficult to broadly keep up with everything that is happening. Somehow, the authors of this book are able to offer real insights in many independent fields.
The book provides many real world examples. It also contains many valuable screenshots of performance monitoring tools under various load conditions. The writing is lucid, thoughtful, and offers many valuable insights. Another feature that I liked is the wealth of references the book offers. I found these references to various web sites, shareware tools, academic papers, and other information sources extremely useful.
The Windows 2000 Performance Guide is a must read for anyone interested in computer performance. Unlike so many other books that I've encountered that are merely a rehash of information available elsewhere, this book is a thoughtful, detailed, and thorough inquiry into its subject matter. Bravo!
If this book somewhere had just a small table saying something about acceptable measured values, and in turn what could be done to change each one, then we'd be getting somewhere. As it is, the book's a mess. The book gives a "starter set" of metrics, but it's on page 110, is six pages long, encompassing probably 100 measurements, and fails to note how the expected results / measurements would be at all connected to controllable factors.
From our perspective, speed was the desired result. It appears using the authors' standpoint and methodology that to buy a new computer would be far more economical than to run all 1200 tests that are poorly explained in this book.