Keeping Track of the Big Picture
Service owners need to worry about their system's big picture, all the time. The big picture isn't just one thing, however — inside that big picture, there are hundreds of tiny components. The foundation of server performance is the constant regulation of all the people and resources that keep the system humming along smoothly. Traditionally, this means not worrying about any single person's (user's) experience when they encounter the system. Service as many requests as possible! Unlike users, whose concerns can be easily summarized in one or two questions (albeit major ones), service owners have a long list of check boxes they need to track. These must all be balanced and juggled, in the name of allocating resources responsibly and effectively. Examples might include:- Is the population running efficiently as a whole?
- Are any outlier users having bad experiences? (Note, however, that this doesn't necessarily mean "What does it feel like for the individual having a bad experience?" — and there's the rub.)
- Are resources being used efficiently?
- How does everything interact?
- This last question introduces a whirlwind of additional, complex inquiries, which need to be weighed and solved in order to answer all the other concerns above.