The first runs a CPU-intensive application ( cpuburn, in particular the burnP6variant), and the second downloads a very large file (1GB). To illustrate the resource utilization of RightLink when performing an additional task (in this case, the running of operational scripts, which were manually triggered, but could also be run via automation) two additional scripts were created. The image above shows the normal state of RightLink when it is installed on a Linux server but is not actively processing any additional user-submitted (or automated) tasks. a single PID displayed per process), the total memory usage was 1.3%, which is approximately 13MB on a t2.micro with 1GB memory. When the collapsed view of htop was used (i.e. These threads share some memory so the total usage is significantly less than the sum of the threads shown. Each RightLink thread is shown as using approximately 1.1% of the available system memory. The above image also shows the memory utilization ( MEM% column) of RightLink on the same quiescent system. The CPU utilization( CPU% column) is negligible (shown as 0%) across all RightLink threads. The figure below shows the CPU utilization of RightLink (shown as /usr/local/bin/rightlink in the Command list) after installation on a quiescent Linux Ubuntu server. The htop utility was used as it allows all threads of a Linux process to be displayed and also facilitates process sorting which enables less cluttered views of the server’s resource utilization.
The resource usage on the Linux server was captured using htop which is an ncurses-based implementation of the standard Linux top utility. The intent of this document is to characterize the resource (CPU, memory and network) utilization of the RightLink agent (version 10.6) on Linux.
0 kommentar(er)
