Software boundaries and limits for Share. Point 2. 01. 3In order to understand the relationship between hardware resources, load and performance, its important to have a way to visualize the factors involved and how they affect each other. Consider the capacity of a farm as a pie, the size of which represents the aggregate of factors such as servers, hardware resources such as CPUs and RAM, storage capacity, disk IOPS, network bandwidth and latency. The size of the pie is therefore related to the overall resources of the farm adding resources such as farm servers increases the size of the pie. This pie is divided into slices that represent load from a variety of sources user requests, search queries, operations against installed features, timer jobs and operating system overhead. Each of these sections must share available farm resources. If the size of one slice increases, the size of others must decrease proportionally. Since load on a farm is not static user requests, for example, might only be significant during certain hours of the day, the relative size of the slices is constantly in flux. However, each slice must maintain a required minimum size to operate normally, and since the functions represented by each slice are interdependent, increasing the size of one slice may place more load on other slices in addition to reducing the resources available for them to consume. Using this metaphor, the goal of the farms design is to make the pie large enough to accommodate the required size of each pie slice under peak load. Now, consider a scenario where user requests increase by 1. Lets say that about half of the requests are search queries, and the other half editing lists and documents. This increased load squeezes the other pie slices, but some farm features must also work harder to compensate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |