Metrics

• File descriptors (valid on UNIX/Linux only)

(Noted as FD in the tables) is a reference to a file opened by the process or a TCP connection, a directory, or a thread. Each process has a system limit that can be verified with the command ulimit -n.

A system command such as: lsof -p <pid> (on Linux) or pfiles <pid> (on Solaris) allows the user to know how much a process consumes.

The limit can be adjusted with the variable UXMAXFD if the system allows it.

• TCP connection between UVMS and the other modules: UVC console, DUAS, UniJob…

Can be captured by the command: netstat -a | grep <UVMS port>

TCP limits the number of port numbers (“MaxUserPort” system settings on Windows) that a process can use at any time. As well, a connection TIME_WAIT is maintained in the system for 4 minutes (“TcpTimedWaitDelay” system setting on Windows) after it closes.

Therefore, if TCP ports are opened and closed often, it can lead the system to reach the MaxUser Port system and no connection will be possible. It will be necessary to increase this limit and to reduce the life of the socket in TIME_WAIT.

• High CPU utilization

This value was measured on quad-cores systems. Therefore, the limit is 400% instead of 100%.

In other words, 100% means that UVMS uses an entire core, 3 cores are still available.

• System Memory Consumption

On Linux, the RSS indicator is measured (Resident Set Size): total memory occupied by product in memory (i.e. swap excluded)

On Windows, the private memory is measured (equivalent indicator to the one on Linux)

• Allocated Memory Heap: piece of memory allocated by Java

The maximum value in UVMS can be defined with the UXMAXJVMMEM UniViewer variable.

The minimum value is defined by the UXMINJVMMEM variable.

The RSS memory (also known as « private memory ») will always be higher or equal to the allocated heap memory. This difference is known as native memory and is used to manage non java object systems, such as thread piles.

• Used Memory heap: refers to the memory quantity used within the heap commonly allocated by Java

If the used heap reaches the allocated heap which is already set to UXMAXJVMMEM, then Java cannot allocate additional memory and errors such as "OutOfMemory" or "Java heap space" may appear in the log file.

• Permanent generation space capacity (PC)

The memory allocated by Java dedicated to persistent objects. This portion of memory is outside of heap. System commands are:

To verify the usage: /<path to jdk>/bin/jstat –gc <jvm pid> and check the PC column

To verify the limits use the command ps –ef | grep <jvm pid> and check the value of the -XX:MaxPermSize= argument

• Permanent generation space used (PU)

The memory used to handle persistent java objects. This portion of memory is outside of heap. System commands are:

To check the usage: /<path to jdk>/bin/jstat –gc <jvm pid> and see PU column

To check the limits: /<path to jdk>/bin/jstat –gc <jvm pid> and see PC column

• Number of threads. Threads are the product sub-processes. Additional threads are created according to the needs to manage user requests or optional services. Threads consume resources: file descriptors, memory. System commands are:

To check the usage: ps –e –o nlwp,pid | grep <pid>

To check the limit: ulimit –u

The related variables are listed below. For more information, refer to section “Dollar Universe Customization”.

UVMS	UNI_VIEWER_MONITORING_CONSOLIDATION_THREADS CHECK_DU_STATUS_PROCESSING_THREADS AUT_THREAD_MIN AUT_THREAD_MAX UNI_VIEWER_PACKAGES_MAX_THREADS
DUAS	U_IO_THREADPOOL_MAX U_IO_THREADPOOL_MIN UXJEE_MAIN_MIN_POOL_SIZE UXJEE_MAIN_MAX_POOL_SIZE UXJEE_SUBMISSION_MIN_POOL_SIZE UXJEE_SUBMISSION_MAX_POOL_SIZE

• Number of used processes

The number of processes with the same name, or created for the same operation (example: the number of processes executing jobs).

To check the usage, the system command is ps –ef | grep <name> | wc –l

To check the limit, on UNIX the system command is linux: ulimit –u, on Windows, check the desktop heap (non-interactive shared section value – see next chapter)

To redefine the system limit, on UNIX/linux the system command is ulimit –u <new value>, on Windows, change the value in the registry (refer to section “Desktop Heap on Windows” for more information)

• Used network bandwidth

The measure of ingoing flow and outgoing used by the product over the network. Transmitted and received data volume for a given operation is also measured.

• Disk I/O: measure of the flow used during disk operations.

Used disk space includes the overall disk space used by file systems, disk space used by each data file (DUAS .dta and .idx files), and disk space used separately by data, binaries and logs.

System commands to check the usage:

df –h

df –i (the inodes table)

du –s –k <directory>

System commands to check the limit:

df –h

A .dta file is currently limited to 2 GB.

Related variables:

U_FS_DATA_WARN_TH

U_FS_DATA_STOP_TH

U_FS_LOG_WARN_TH

U_FS_LOG_STOP_TH

U_FS_FILESIZE_WARN_TH

U_FS_FILESIZE_STOP_TH

• Response time: amount of time taken by the product to perform a given operation completely.