Skip to main content
Skip table of contents

Interpreting performance statistics for NexJ CRM

Performance statistics display request and response metrics for the user, providing detailed information on browser-to-server requests in real time.

Use this functionality to identify network and environment issues in your application deployment. This helps application developers and quality assurance analysts understand potential performance bottlenecks, detect performance regressions, and investigate environment issues such as database performance.

As of NexJ CRM 9.4, application developers, solution architects, or QA analysts, can click the Show available actions floating action button in the bottom-left corner of the user interface to display the summary of server, network, and client performance statistics.

The following screenshot shows the floating action button and the available statistics:

Show available actions floating action button example

The value displayed in each property label is the maximum value of the last 10 summarized entry values for that property.

The numbers displayed on the labels are rounded to the nearest integer above them, however for numbers less than 10 the values display one decimal digit.

If the user is curious to know more details about the performance statistics for each event, the user can click More Details to open the Performance statistics dialog that contains further details. The Performance statistics dialog contains the following information.




The event or user action that occurred.


The path to the target view of the event, if available.

Request TypeThe type of resource that was requested for the event.
Start time (ms)The time at which processing of the event is started.

End time (ms)

The time at which processing of the event is ended.

Lazy load (#)

The number of lazy loads the server did while handling the request.

RPC (#)

The number of remote procedure calls to the server while handling the event.

SQL (#)

The number of SQL queries the server made while handling the request.

Server (ms)

The time it took for the server to handle the request in milliseconds.

SOA (#)

The number of SOA calls made to the server.

SOA depth

The maximum call depth reached by any single SOA call.

Response (KB)

The size of the body of the response in KB.

Network (ms)

The network processing time in milliseconds.

Update cycles (#)

The number of times the application went through retrieving and rendering the information while handling the event.

Render (ms)

The time it took to render the information in the browser while handling the event.

Browser (ms)

The processing time of the event in the browser while handling the event.

Total (ms)

The sum of the network, server, and browser execution time in milliseconds.


The following metrics are displayed in the floating action button:


The time it took for the server to handle the request in milliseconds.


The size of the body of the response in KB.


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).


The time the browser took to process the response in milliseconds.

Color coding

The following default threshold values determine the color of the statistics icons.

By default, the statistics icons display as green icons. Green icons indicate favorable performance while red icons indicate potential environment issues. Contact your system administrator if your NexJ application regularly displays red statistics icons.

Threshold values

PropertyYellow thresholdRed threshold
NetData (KB)7001575
NetTime (ms)250450
Server (ms)500850
Client (ms)10001750
Total (ms)15002500

If a performance statistics icon 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.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.