Skip to content
  • There are no suggestions because the search field is empty.

The nim-fastpoll process is using too much memory.

The Statseeker server is showing very high memory usage for the nim-fastpoll process.

Statseeker 5.6.1 has a memory leak for the real-time polling tool which can use a large amount of the Statseeker host's memory.

This bug is fixed in Statseeker 5.6.2.

Below is an example of the Real Time Polling running:

The command line shows the process for this:

statseeker$ ps -auwx | grep nim-fast
statseeker 62802   1.0  0.1   21948   6784  -  Ss   Tue07        8:34.61 nim-fastpoll
statseeker 39861   0.0  0.0   12872   2040  0  S+   14:14        0:00.00 grep nim-fast

The currently running Real Time Poller's memory usage can be killed by:

As Admin, go to > Admin Tool GUI > Statseeker Administration section > Services > Edit mode (in blue upper right corner of the page) and then scrolling down the Nim-fastpoll Daemon line and clicking the "Restart" button and then click "Yes" on the window that pops up:

Statseeker will then have a new process ID for the nim-fastpoll process and the Real Time Poller will have it's statistics collection reset.

statseeker$ ps -auwx | grep nim-fast
statseeker 42235   1.0  0.1   19388   6856  -  Ss   14:26        0:00.00 nim-fastpoll
statseeker 42270   0.0  0.0   12872   2044  0  S+   14:26        0:00.00 grep nim-fast