The ideal way to pinpoint the cause of any CPU utilization is to narrow down the cause to a specific thread.
To get the PID of the netsight process
To get a java thread dump of the netsight process into a file jstack.out
./jstack <PID> > jstack.out
To get information about CPU use in threads, but don’t show idle threads, and sort the output from highest CPU to lowest.
ps -L -o pid,tid,%cpu <PID> | grep -v "0\.0" | sort -g -r -k 3,3
The second column of this ps command is the thread ID, in decimal. This corresponds to the “nid” (native id) value shown in the java thread dump, which is in hexadecimal.
$ cat /var/run/nsserver.pid
$ cd /usr/local/Extreme_Networks/NetSight/java/bin
$ ./jstack 5552 > jstack.out
$ ps -L -o pid,tid,%cpu 5552 | grep -v "0\.0" | sort -g -r -k 3,3
5552 5717 9.8
5552 5718 1.3
5552 5570 1.2
$ printf "%x\n" 5717
$grep 1655 jstack.out
"Flow Engine - Active Flow Aging Timer" prio=10 tid=0x00007fba91ead800 nid=0x1655 in Object.wait() [0x00007fba49733000]