CHAPTER 10 JAVA EE PERFORMANCE ASSESSMENT Figure (Web hosting reviews)
CHAPTER 10 JAVA EE PERFORMANCE ASSESSMENT Figure 10-10 displays the same requests, but sorted by maximum response time. While the third request completed with an acceptable average response time (1.657 seconds), its maximum response time was almost 47 seconds. When things went bad, they went very bad! Figure 10-10. Requests sorted by their maximum response times Figure 10-11 displays the same requests, but sorted by total response time. While the fourth request completes with an acceptable average response time (0.878 seconds), it is executed 1,248 times, yielding a total response time of 1,095 seconds. Each of the aforementioned requests deserves attention and deeper diagnostics. You cannot simply look at requests that perform slowly on average; you must also include those with periodic spikes and those that significantly impact the performance of the application because of their call counts. The difference in diagnostics is that tuning average slow-running requests is a reactive process, while tuning requests with heavy impact is a proactive process to improving application quality. But as you can observe from Figures 10-9 through 10-11, there is a great deal of overlap: requests that average slow response times usually have spikes and are often called frequently.
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.