Netgate 2100 Max CPu pings 100% when download large files

northernsky

@stephenw10 OK sounds good. I think we I can close this one out. I do have a couple questions. Is it worth installing the bandwidhd or traffic totals packages? I guess is probably a good time for me to re-check to make sure I am using the best practices and was wondering if you knew a good website resource from netgate?

SteveITS

@northernsky What you install is up to you/dependent on what you need. Something that counts bytes or scans packets is going to take CPU cycles per packet.

FWIW we have bandwidthd installed on one router out of several dozen (us and clients) and it’s for a specific reason.

Gertjan

@northernsky said in Netgate 2100 Max CPu pings 100% when download large files:

Is it worth installing the bandwidhd or traffic totals packages?

These create stats. Loads of stats.
This means :
They need 'a lot of space' to store the stats (so your disk storage device will be used way more faster ... and remember : these don't live forever, they have a max write cycle live time)
They 'tap' into the network driver(s) to get access to the real time data (packet) flow, and pareses every one of them. Probably only the headers, but still : overall impact will be noticeable.
They will 'log' a lot, so again : disk space and a lot of writes cycles.

It's always the same : even it's is free, there is a price and performance tradeoff. You decide what's OK for you.

Btw : your last image : I see several identical dpinger processes using 76.135.2xx.111.
Normally, there is only one (two) dpinger process(es) - one for every IP type : IPv4 and IPv6.
Not sure why you have several of them.

I have an IPv4 and IPv6 connection, so :

northernsky

@Gertjan

Odd I see them too but they use the same pid. Not sure why there are multiples displayed there.

Gertjan

@northernsky said in Netgate 2100 Max CPu pings 100% when download large files:

same pid

Ah, ok. Seems less fishy then.

dennypage

@Gertjan said in Netgate 2100 Max CPu pings 100% when download large files:

Btw : your last image : I see several identical dpinger processes using 76.135.2xx.111.
Normally, there is only one (two) dpinger process(es) - one for every IP type : IPv4 and IPv6.
Not sure why you have several of them.

He is using the System Activity page rather than the ps command. The System Activity page uses the command:

/usr/bin/top -baHS 999

A somewhat equivalent ps command would be:

/bin/ps -axlrHwwww

The -H option for both means list all threads.

dpinger uses dedicated threads for its tasks. In pfSense, dpinger will have 5 threads:

Main process control thread
ICMP sender thread
ICMP receiver thread
Alert monitor thread
UDP socket status thread

There is a potential 6th thread, the reporting thread, but this is not used in pfSense. pfSense polls the UDP socket instead.

I'm expect this is more than you ever wanted to know about dpinger.

northernsky

@dennypage

The more you know.

Lots of tribal knowledge out there so you do us all a solid by sharing. :)

Gertjan

@dennypage said in Netgate 2100 Max CPu pings 100% when download large files:

/usr/bin/top -baHS 999

Didn't saw him using that command ...
Thanks, now knowing this, I'm seeing the same results.
And top ? switched to htop ages go me.

northernsky

@stephenw10

Any idea when the next update will be out?

stephenw10

It's in beta now. I'm running it in "production" and see no issues. That may not be an option for you though.

Hard to give anything certain but we are looking at weeks I think.