Interpreting performance banners
Performance banners display request and response metrics on a color-coded background.
Performance banners contain the following information:
Sample performance banner
Metrics
The following metrics are displayed in each performance banner:
Timestamp
The time the portlet's HTTP request was made.
Total
The sum of the network, server, and JavaScript execution time in milliseconds.
Network
The network processing time in milliseconds.
Since there is no way to determine when GET requests originated, the Network value of GET requests is set to N/A (not available).
JS
The time the JavaScript took to process the response in milliseconds.
Server
The time it took for the server to handle the request in milliseconds.
SOA
The number of SOA calls made to the server and maximum call depth reached by any single call.
SQL
The number of SQL queries the server made while handling the request.
Lazy Load
The number of lazy loads the server did while handling the request.
Size
The size of the body of the response in KB.
Color coding
The following default threshold values determine the color of the performance banner. Green indicates favorable performance while red is an indication of a potential environment issue. Contact your system administrator if your NexJ application regularly displays red performance banners.
Performance banner default threshold values for desktop and laptop computers
| Color | Total time | Response size | SQL | Lazy load |
|---|---|---|---|---|
| Green | 0-750 ms | 0-200 KB | 0-15 | 0-5 |
| Yellow | 750 - 1500 ms | 200 - 400 KB | Not applicable | 5 - 10 |
| Red | 1500 ms | 400 KB or more | 15 or more | 10 or more |
Performance banner default threshold values for mobile devices
| Color | Total time | Response size | SQL | Lazy load |
|---|---|---|---|---|
| Green | 0-750 ms | 0-200 KB | 0-15 | 0-15 |
| Yellow | 750 - 1500 ms | 200 - 400 KB | Not applicable | 15-30 |
| Red | 1500 ms or more | 400 KB or more | 15 or more | 30 or more |
If a performance banner is red due to a network, JS, or server response, it is highly advisable to attempt to reproduce the issue to ensure that it is consistent and not just sporadic. Performance issues may not be actionable if they are not occurring fairly consistently.
Merged performance metrics
Merged performance metrics display two sets of data in a portlet's performance banner.
The banner displays information about the two requests executed when a dialog is opened or closed. Merged performance metrics are separated with a comma and are displayed in the order in which they occurred.
Merged performance metrics provide you with a complete analysis of multi-step processes in your NexJ application.