-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sampling rate option of nProbe is not working properly #572
Comments
This is the format As you are collecting packets you need to use -S "10:1:1" as you did. However, from the report, it is unclear if you are using PF_RING. Can you please check that and report it? Furthermore have run a few tests and everything seems to work. The difference between our lab and you is that you are capturing a lot of traffic without ZC. I have the feeling that you have severe drops. In this case sampling can screw up everything, So I suggest you check drops (add -b=1) and then eventually apply -S. If you do not want to use ZC, please at least enable RSS. |
Even after upgrading nProbe to the latest version(10.3.230302), the memory issue still remains.
So, alternatively, I'm trying to use the sampling rate option(-S="10:1:1") in order to reduce the memory usage.
But, sampling rate is not working properly.
I'm expecting that the Rx/Tx should be the same as before even though nProbe throughput will be reduced to 1/10.
However, the Rx/Tx is increasing almost by 100 times after setting "sample rate" option to "10:1:1".
Do you have any idea about this issue?
Here is the configuration of our nprobe.conf:
-I=nProbe
--zmq="tcp://192.168.0.X:5556"
--zmq-probe-mode
-i=enp3s0
-n=none
-T="@ntopng@"
-b=1
-f="ip proto not 50"
-S="10:1:1"
The text was updated successfully, but these errors were encountered: