Hi Chander,
I am unable to confirm your figure but i can say that you can give a try
to PF_RING-enabled libpcap to see if it brings any advantage to the
performance you are currently seeing.
Also, as explained here (
https://github.com/pmacct/pmacct/blob/50c6545275ba8fdf227a248af9982302f1ef25e0/QUICKSTART#L243-#L255
) with PF_RING and a supported NIC you can scale performance
horizontally by hashing flows over NIC queues and then binding pmacctd
to a specific NIC queue.
Paolo
On 1/12/22 05:54, Chander Govindarajan wrote:
Hi,
Wanted to check what the expected performance of pmacctd is for the
following config. Using pmacctd (v1.7.7 docker image with nfprobe plugin
on an Ubuntu 22.04, linux kernel 5.15) with the key portion of the
config as follows:
```
aggregate: src_host, dst_host, in_iface, out_iface, timestamp_start,
timestamp_end, src_port, dst_port, proto, tos, tcpflags
timestamps_secs: true
plugin_pipe_size: 102400
nfprobe_timeouts:
tcp=5:tcp.rst=5:tcp.fin=5:udp=5:icmp=5:general=5:maxlife=5
sampling_rate: 20
```
With iperf2 (-l 1440 -P 1 -b 1G) and around 100k packets per second, I
am seeing CPU util of ~25-30% by pmacctd. Is this within expected
behaviour?
Regards,
Chander
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
