This is no surprise. Lcore 1 is running at the max vector size, indicating that it’s completely out of clock cycles / dropping traffic. Moreover:
Node Name Clocks/Pkt TenGigabitEthernet6/0/1-output 8.67E+00 TenGigabitEthernet6/0/1-tx 1.08E+02 error-drop 4.15E+01 ip4-arp 3.43E+01 ip4-drop 8.91E+00 ip4-input-no-checksum 3.77E+01 ip4-lookup 2.98E+01 ip4-mimic-classify 2.13E+02 ip4-rewrite 2.96E+01 lookup-ip4-src 5.07E+01 snat-in2out-fast 2.56E+02 Total clocks/pkt 8.18E+02 Packet I/O rate 2.22E+06 Imputed CPU clock rate 1.82E+09 Just to ask: does the CPU chip involved have an actual clock rate of around 2gHz? The way the computation is running, the snat in2out path - and whatever “ip4-mimic-classify” is - run on lcore 1. The snat out2in path runs on lcore 2. The out2in path is faster than the in2out path. HTH… Dave From: [email protected] [mailto:[email protected]] On Behalf Of ?? Sent: Friday, July 14, 2017 11:12 PM To: [email protected] Subject: [vpp-dev] Why VPP drop packets while the average vectors per node is still low Hi, guys Last week I did some performance test on VPP with Spirent testcenter. Below I give two groups of running data in two different situation using the 'show run' command . In both situation VPP drop packets ( from the 'rx-miss' output in 'show int' command). In my opinion, when VPP begins to drop packets, the value of Vectors/Call should be high. So I think situation 1 is easy to understand. But the running data of situation 2 make me confused because Vectors/Call is still very low. Can anyone explains why and what's the relationship between VPP performance and average vectors per node? --------------------------------------------------------situation 1------------------------------------------------------------------- Thread 1 vpp_wk_0 (lcore 1) Time 225.3, average vectors/node 255.99, last 128 main loops 0.00 per node 0.00 vector rates in 2.2244e6, out 2.2242e6, drop 2.0019e2, punt 0.0000e0 Name State Calls Vectors Suspends Clocks Vectors/Call TenGigabitEthernet6/0/1-output active 1957460 501107294 0 8.67e0 255.99 TenGigabitEthernet6/0/1-tx active 1957460 501107294 0 1.08e2 255.99 dpdk-input polling 1227897513 501152389 0 4.65e2 .41 error-drop active 182 45103 0 4.15e1 247.82 ip4-arp active 138 34616 0 3.43e1 250.84 ip4-drop active 44 10487 0 8.91e0 238.34 ip4-input-no-checksum active 1957630 501152389 0 3.77e1 255.99 ip4-lookup active 1957630 501152389 0 2.98e1 255.99 ip4-mimic-classify active 1957630 501152389 0 2.13e2 255.99 ip4-rewrite active 1957452 501107286 0 2.96e1 255.99 lookup-ip4-src active 1957630 501152389 0 5.07e1 255.99 snat-in2out-fast active 1957630 501152389 0 2.56e2 255.99 --------------------------------------------------------situation 2------------------------------------------------------------------- Thread 2 vpp_wk_1 (lcore 2) Time 1024.5, average vectors/node 8.57, last 128 main loops 0.00 per node 0.00 vector rates in 1.2209e6, out 1.2209e6, drop 0.0000e0, punt 0.0000e0 Name State Calls Vectors Suspends Clocks Vectors/Call TenGigabitEthernet6/0/0-output active 145982828 1250882588 0 2.93e1 8.57 TenGigabitEthernet6/0/0-tx active 145982828 1250882588 0 1.37e2 8.57 dpdk-input polling 9106470948 1250882588 0 1.31e3 .14 ip4-input-no-checksum active 145982828 1250882588 0 7.39e1 8.57 ip4-lookup active 145982828 1250882588 0 7.56e1 8.57 ip4-mimic-classify active 145982828 1250882588 0 1.31e2 8.57 ip4-rewrite active 145982828 1250882588 0 6.33e1 8.57 snat-out2in-fast active 145982828 1250882588 0 4.50e1 8.57
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
