ProSBC processor Usage - Revision history

Luc Morissette: Updated TOC and formatting

2021-03-11T16:46:24Z

Updated TOC and formatting

Luc Morissette at 16:36, 11 March 2021

2021-03-11T16:36:51Z

Luc Morissette: New wiki page for ProSBC processor usage

2021-03-11T16:32:51Z

New wiki page for ProSBC processor usage

New page

{{DISPLAYTITLE:ProSBC Processor Usage}}

This procedure is used to check the Processor usage of the ProSBC. 

== How to check Processor usage from the web portal ==
From the web interface you can see the processor usage: 
Hosts -> Status -> Select Host -> Processor Usage tab

Totals view show the global processor usage, and processor usage divided between applications and SBC processing 
[[image:SBC_Processor_usage.png]] 

Packet Processing shows processor usage of each IP interfaces 
[[image:SBC_Processor_usage_pkt.png]] 

Applications shows the processor usage of the individual applications and their theoretical maximums 
[[image:SBC_Processor_usage_app.png]] 

== Accessing from the console ==
From the [[Accessing_Device#SSH|SSH access]], here are the available commands. 
With the '''top''' command you can see the total CPU usage (and Memory usage) of the host:
# top
top - 07:27:40 up 13 days, 17:50, 1 user, load average: 1.29, 1.38, 1.54
Tasks: 140 total, 1 running, 139 sleeping, 0 stopped, 0 zombie
%Cpu(s): 26.0 us, 3.6 sy, 0.0 ni, 70.2 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st
KiB Mem : 8042848 total, 1864328 free, 3560852 used, 2617668 buff/cache
KiB Swap: 2097148 total, 2097148 free, 0 used. 4157628 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
708 root 20 0 65.1g 240676 17260 S 101.3 3.0 20052:50 tbrouter
863 root 20 0 0 0 0 S 8.0 0.0 1636:13 kni_single
8276 root 20 0 2046568 146152 5808 S 1.7 1.8 214:46.81 tbsip
3495 root 20 0 1996260 127884 5972 S 1.3 1.6 258:41.70 toolpack_engine
3690 root 20 0 2543928 109644 6904 S 1.3 1.4 320:42.86 gateway
3181 root 20 0 10876 672 536 S 1.0 0.0 224:56.18 ipwatchd
...
 
Here we see the processor usage is 70% idle. 
We also see the tbrouter application is at 101% CPU, which is normal. You can have more details here: [[Toolpack_Application:tbrouter]] 
 

=== Periodic logs on processor usage ===
Processor and memory usage are logged on the system. You can get access to these logs in this folder:
/lib/tb/toolpack/setup/12358/3.1/apps/tboamapp/log
It is also available in the [[TBreport]]

@@ Line 3: / Line 3: @@
 This procedure is used to check the Processor usage of the ProSBC.<br>
-== How to check Processor usage from the web portal  ==
+== How to check processor usage from the web portal  ==
 From the web interface you can see the processor usage:<br>
    Hosts -> Status -> Select Host -> Processor Usage tab
+<br>
 Totals view show the global processor usage, and processor usage divided between applications and SBC processing <br>
 [[image:SBC_Processor_usage.png]]  <br>
+<br>
 Packet Processing shows processor usage of each IP interfaces <br>
 [[image:SBC_Processor_usage_pkt.png]]  <br>
+<br>
 Applications shows the processor usage of the individual applications and their theoretical maximums<br>
 [[image:SBC_Processor_usage_app.png]]  <br>
+<br>
 == Accessing from the console ==
@@ Line 43: / Line 43: @@
 Processor and memory usage are logged on the system. You can get access to these logs in this folder:
   /lib/tb/toolpack/setup/12358/3.1/apps/tboamapp/log
-It is also available in the [[TBreport]]
+It is also available in the [[TBReport]]

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:ProSBC Processor Usage}}
+__TOC__
 This procedure is used to check the Processor usage of the ProSBC.<br>
@@ Line 15: / Line 15: @@
 Applications shows the processor usage of the individual applications and their theoretical maximums<br>
 [[image:SBC_Processor_usage_app.png]]  <br>
-<br>
+<br><br>
 == Accessing from the console ==
 From the [[Accessing_Device#SSH|SSH access]], here are the available commands. <br>
 With the '''top''' command you can see the total CPU usage (and Memory usage) of the host:
-  # top
+  [root@prosbc-vm-a1]# top
-top - 07:27:40 up 13 days, 17:50,  1 user,  load average: 1.29, 1.38, 1.54
+<br>
-Tasks: 140 total,   1 running, 139 sleeping,   0 stopped,   0 zombie
+ top - 07:27:40 up 13 days, 17:50,  1 user,  load average: 1.29, 1.38, 1.54
-%Cpu(s): 26.0 us,  3.6 sy,  0.0 ni, 70.2 id,  0.0 wa,  0.0 hi,  0.2 si,  0.0 st
+ Tasks: 140 total,   1 running, 139 sleeping,   0 stopped,   0 zombie
-KiB Mem :  8042848 total,  1864328 free,  3560852 used,  2617668 buff/cache
+ %Cpu(s): 26.0 us,  3.6 sy,  0.0 ni, 70.2 id,  0.0 wa,  0.0 hi,  0.2 si,  0.0 st
-KiB Swap:  2097148 total,  2097148 free,        0 used.  4157628 avail Mem
+ KiB Mem :  8042848 total,  1864328 free,  3560852 used,  2617668 buff/cache
+ KiB Swap:  2097148 total,  2097148 free,        0 used.  4157628 avail Mem
-  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 root      20   0   65.1g 240676  17260 S 101.3  3.0  20052:50 tbrouter
 root      20   0       0      0      0 S   8.0  0.0   1636:13 kni_single
@@ Line 34: / Line 46: @@
 root      20   0 2543928 109644   6904 S   1.3  1.4 320:42.86 gateway
 root      20   0   10876    672    536 S   1.0  0.0 224:56.18 ipwatchd
 <br>
 Here we see the processor usage is 70% idle. <br>
 We also see the tbrouter application is at 101% CPU, which is normal. You can have more details here: [[Toolpack_Application:tbrouter]] <br>
 <br>