Next, we might try looking at the download (Apache web server)
Next, we might try looking at the download times of the various pages to see how the item detail page stacks up. The download times are shown in Figure 17-6. Figure 17-6. Page download times of the Storefront application As you can see, tracking down performance problems involves some detective work. You have to look behind every corner and leave no stone unturned. 17.4.4 Make the Necessary Changes to Software and Hardware Once you think you’ve found the problem and made the necessary changes, go back to the testing scripts once again. Keep doing this over and over until all of the performance issues are solved or it’s time to ship the product. Because time is limited, it’s vital that you plan your testing activities to cover the largest areas of the application and to focus on specific components that are known to cause performance or scalability problems. There’s usually not just one problem to fix it’s a constant back-and-forth process that could go on forever, except for the fact that you eventually have to ship the product. It’s imperative that you concentrate on the biggest performance areas first. 17.5 Performance and Scalability Gotchas This section presents several well-known issues that may affect performance and scalability for your Struts applications. This section is not meant to be exhaustive, but rather to single out a few of the more serious concerns. 17.5.1 Request Scope Versus Session Memory is limited. You can purchase more memory for a machine, but at some point you’ll stop receiving the same return on your investment. It’s very common to store objects and data in the user’s
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check mysql web server services.