Running Performance Tests for NDIS Miniport Drivers (Windows CE 5.0)
To measure the performance of the miniport driver at NDIS and Winsock levels, run the NDIS Performance Test and Winsock Performance Test Cases
The following illustration shows the test configuration.
To run the performance tests
Use the Perf_ndis tool to enumerate the miniport driver instances present on your Windows CE-based device.
tux -o -d perf_ndis -c "-enum"Run the NDIS Performance Test by using the Perf_ndis tool.
Use the following command to measure the send throughput
tux -o -d perf_ndis -c "-mode send -wsock -s <Miniport Driver Instance>"Use the following command to measure the recv throughput
tux -o -d perf_ndis -c "-mode recv -wsock -s <Miniport Driver Instance>"
If the performance of the miniport driver is lower than expected, use the Monte Carlo Profiling tool during the test to determine the components that take up most of the transfer time.
Run the Winsock Performance Test by using the Perf_winsock tool.
This test is optional if you have already run the Winsock Stress Test described in Running the Winsock Stress Test. The test criteria for this test depend on the following factors.
- The hardware platform for the Windows CE-based device. For example, CPU, CPU speed, R/W RAM, type, and amount of cache memory.
- NIC hardware.
- Type of bus the NIC is based on, such as SDIO, PCMCIA, PCI.
- Type of network, such as Wired regular 10/100 mbps LAN, 802.11b Wi-Fi network.
- Miniport driver
- Bus driver or any driver in the stack and platform code.
See Also
How to Develop a Connectionless NDIS Miniport Driver | How to Test an NDIS Miniport Driver
Send Feedback on this topic to the authors