Exercise 1: Latest Orders Page

The latest orders page should display the last 50 orders that have been made on our DVD Store. This way the user can check what other people have been ordering lately. This example can show that even with simple use case we can have performance problems, even if you have the feeling that the page is loading quite fast. Remember that you are the only user accessing the application, and that more users accessing it at the same time can slow it down. 

What do you need to do?

1. Activate the performance problem Slow Display of Latest Orders Page if you did not do it already
2. Go to the Latest Orders page
3. Analyze the results of monitoring with the inspectIT User interface

Your task

• Find the performance problem in latest order page.

Solution hints:

• The business service method that processes the request is findLatestOrders() in the LatestOrdersAction class.
• Is there something wrong with the SQL Statement(s) that is/are executed if you compare them to the statements executed with the problem deactivated?
• Is there something done unnecessary?

Optional

In real world scenario you would maybe like to send the data showing the performance problem to the developer (or attached it to Jira). You can do this by saving the slow request you identified to storage, exporting the storage to a file and sending the file per mail. Please perform this and send created .itds file to your mail address. It’s often interesting to provide additional information with the storage that contains the problematic performance data. The inspectIT provides means to categories the storages based on the labels. Thus, please add two labels to the storage:

• Add already existing Status label with value In Progress
• Create new label type Impact and define a value of your choice on 1-10 scale.