Closed rajeshwarp2002 closed 1 year ago
so when throughput is very low or f-stack application is running at ver low cpu, even if multiple instances are spawned they ddon't show any any gain in perf. Actual gain in perf is seen at higher rates when f-stack app is overloaded. Hence closing this one
Hello F-stack team,
I am seeing this weird issue where I have two processes, primary and secondary. All my http flows are equally divided among them, but I see increase in latency. I went through existing issues but couldn't find anything conclusive.
thanks
NIC details: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection EAL: Detected CPU lcores: 32 EAL: Detected NUMA nodes: 2 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: No available 1048576 kB hugepages reported EAL: Probe PCI driver: net_ixgbe (10fb) device: 0.1 (socket 0) TELEMETRY: No legacy callbacks, legacy socket not created f-stack -c4 -n4 --proc-type=primary lcore: 2, port: 0, queue: 0 create mbuf pool on socket 0 create ring:dispatch_ring_p0_q0 success, 2047 ring entries are now free! create ring:dispatch_ring_p0_q1 success, 2047 ring entries are now free! Use symmetric Receive-side Scaling(RSS) key Port 0 modified RSS hash function based on hardware support,requested:0x2003ffffc configured:0x38d34 RX checksum offload supported TX checksum offoad is disabled TSO is disabled port[0]: rss table size: 128
RSS hash function: toeplitz: on xor: off crc32: off
[root@localhost ~]# ethtool p7p1 Settings for p7p1: Supported ports: [ FIBRE ] Supported link modes: 10000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 10000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 10000Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes