Performance optimization of our development often do. Usually we will do something in the code level optimization, or transformation at the process level, basic little optimized architecture level. Architecture generally overthrow reconstruction.
"Performance of the summit" This book is the second brush. The first look at this book, the only impression left is 3.3Hz CPU register delay explanation, I realized the huge gap between the hard disk read and write and network transmission with CPU operation.
This gap has spawned many algorithms to solve the problem from the software level with the data structure, such as a database index B + tree, such as a variety of queuing models.
The so-called performance, in fact, two core points: latency and throughput. For example, in "HTTP Definitive Guide," which talked about things in the performance of HTTP, the most critical is the delay. From [the DNS query, connection request processing, the respective closed] Processed whole link, the focusing properties of each region are critical nodes.
Load performance is a key point mutations. For example, the network is busy cause performance degradation, with too many cars highway makes mention speed up the same. So there have been a lot of tools to monitor the load, for a variety of performance issues, optical passive monitoring is not enough, have to take the initiative to analyze.
Based on the use of these tools, a method of forming a system. Tools such as law, USE method, random changes in law ...
Doing low-level performance monitoring, there are still the core system routines.
Such as operating systems, various sources of observation / proc and / sys file system.
In such applications, the IO substantially bottlenecks, cache, buffer, garbage collection here.
Next comes the CPU, memory, file system, disk, network, this 5 core knowledge points.
In a book, encompasses several core modules of the operating system, you can guess certainly not exhaustive, so the focus of this book is a variety of command tool.
So, this book is a another level of understanding from the toolbox brochures, categories were summarized, and provided the correct use. After studying the book, and you will not try to do this operation with an ax chopping. Because this book is similar with the "design data-intensive applications," strategically advantageous position, so the CPU, memory, file system, disk, network of these core knowledge points, still need to be supplemented from other books.