Hi, >From your results it seems for that traffic is not balanced between workers, >and you may have situation when single worker receives all traffic and trying >to distribute to other ones.
Make sure to look at rx placement and hashing in `vppctl show hardware-interface`. Each worker should have own rx queue for involved hardware interface, and their distribution should be balanced, so traffic is balanced as well. Like 3 workers = 3 interface rx queues. And that hash is working you can check via `vppctl show run | grep node-name-which-distributes-packets` - it should show that node counters increase similarly, aka balanced. 1. 2048 should be more then enough. In my testing I had zero drops with default value of 64 to up of 4 workers. For more workers it can be increased. 2. If packets are balanced and loss still persist, then instead of increasing queue size figure out why packets are not processed fast enough on the other end. Queue exists only to preserve packets for target worker to finish his current graph loop + possible lags on both sides. Making queue larger will cover more lags of target worker, but I suggest trying to figure why node lag happens in the first place using perf. 3. Having single per-worker queue per-node/plugin is optimal for most cases. Can you include more information: configuation, worker counts, speeds, how much traffic is handled by single worker?
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26671): https://lists.fd.io/g/vpp-dev/message/26671 Mute This Topic: https://lists.fd.io/mt/116856661/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
