IO Issues: Remote Socket Accesses
- Local socket: I/O device is attached directly to the socket where the I/O is consumed/produced.
- Remote socket: I/O device and a core consuming/producing data belong to different sockets. I/O data has to traverse the Intel QuickPath Interconnect (Intel QPI) to reach the consuming core
- Application: Intel® Data Plane Performance Demonstrators (Intel DPPD) PROX application that performs L2 forwarding to port 1 of packets received on port 0.PROX is configured in two ways as follows:Local socket: DPDK is pinned to a core on socket 0Remote socket: DPDK is pinned to a core on socket 1
- Intel VTune Amplifier 2018: General Exploration analysis
- All the Cookbook recipes are scalable and can be applied to Intel VTune Amplifier 2018 and higher. Slight version-specific configuration changes are possible.
- Intel® VTune™ Amplifier has been renamed to Intel® VTune™ Profiler starting with its version for Intel® oneAPI Base Toolkit (Beta). You can still use a standalone version of the VTune Profiler, or its versions integrated into Intel Parallel Studio XE or Intel System Studio.
- Operating system: Red Hat* Enterprise Linux Server 7.4
- CPU: 2x Intel Xeon processor E5-2695 v4 with Intel DDIO, which is a dual-socket system consuming data packets from the NIC (System Under Test) and the traffic generator (GEN)
Run General Exploration Analysis
- Find out the PID of the running PROX:ps aux | grep prox
- Run the General Exploration analysis with the VTune Amplifier command-line interface (amplxe-cl) and attach to the running PROX process:amplxe-cl -collect general-exploration -knob collect-memory-bandwidth=true -r <result_dir> --duration 25 --target-pid <PID>