Scalability and Diminishing Returns

If an application is designed to scale (vertical, or scaling up to faster resources is easy), the question becomes, “How many resources are enough?” Keep in mind that you will start a scaling process to meet performance requirements based upon user demand. To measure performance, you should select meaningful benchmarks:

  • Support for 5000 simultaneous users

  • CPU utilization does not exceed 50 percent

  • Home page loads in 3 seconds or less

  • All pages load in 5 seconds or less

  • User submit operations should complete in 10 seconds or less

With your selected benchmarks in place, you can then begin to measure the performance effects of scaling. At first, adding a faster processor, more servers, or increased bandwidth should have measurable system performance improvements. You will reach a point, however, based upon diminishing returns, as shown in FIGURE 19-7, for which adding additional resources does not impact performance. At that point, you should stop scaling.

A line graph shows resource scaling on the horizontal axis and performance on the vertical axis with the line rising up in performance up to a certain point of resource scaling and then moving flat.

FIGURE 19-7 Based on diminishing returns, you will reach a point when further scaling does not significantly improve application performance.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset