latencyspikes of seconds (<3s) during speed test on an atom E3940

Started by thelittleblackbird, June 26, 2026, 10:52:00 PM

Previous topic - Next topic
Quote from: thelittleblackbird on June 27, 2026, 12:42:34 AMhere you have it, in the attached file.

I tried to implement the tunnable described in the opnsense documentation about performance:
https://docs.opnsense.org/troubleshooting/performance.html

if you need something else just ask

thanks


If you have set RSS for that performance, it might need revisiting. Maybe it does not help and is detrimental in your case.

Quote from: pfry on June 30, 2026, 11:37:34 PMHow about the PCI query?

not a single error logged, see attached file

Quote from: pfry on June 30, 2026, 11:37:34 PMIt could be a software issue. My experience is limited to a couple FreeBSD and a couple OPNsense machines, all bare-metal. Recent/relevant experience, that is. Most of the pf messages could point to really wacky network issues, but (in particular) I wouldn't expect a duplicate flow ID to be a soft issue (within the scope of a standard OPNsense install). I just don't have enough experience poking into pf to say with certainty.

same for me, i dont have a lot of experience with BSD in general and opnsense in particular, but in  my particular experience all these messages about bad states in the state connection table sound strange.

Thanks for the ideas anyway

Quote from: cookiemonster on Today at 12:17:06 AMIf you have set RSS for that performance, it might need revisiting. Maybe it does not help and is detrimental in your case.

The problem was present before that optimization, in fact i thought that the problem was there because I selected "safe defaults".


Quote from: thelittleblackbird on Today at 10:07:11 AMnot a single error logged, see attached file[...]

Ha! Much cleaner than the ones I have handy to check (AMD CPUs, with most stuff at v2-4).

Well, good luck with it.