IOCREST PCI-E 2.5Gbps NIC ( RTL8125B ) Benchmark

Below are some basic iperf benchmarks of the IOCREST PCI-E 2.5Gbps NIC. The adapter is confirmed to be using a Realtek RTL8125 series chip - specifically the marketing for this card states it's an RTL8125B, it simply shows as RTL8125 through lspci and lshw under the product field, however you can see under the configuration field it states firmware=rtl8125b-2_0.0.2.

This is a very common Realtek chip used for a lot of 2.5Gbps NICs and you'll likely see the same one in use across many similar cards across a range of vendors. The testing was performed using a direct connection between the NIC and another device that also has a RTL8125 based 2.5Gbps NIC.

The card costed me roughly ~$16 AUD from AliExpress.

Hardware details
$ sudo lshw -class network

  *-network
       description: Ethernet interface
       product: RTL8125 2.5GbE Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: <REDACTED>
       logical name: <REDACTED>
       version: 05
       serial: <REDACTED>
       size: 2500Mbit/s
       capacity: 2500Mbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd 2500bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.8.11-300.fc40.x86_64 duplex=full firmware=rtl8125b-2_0.0.2 07/13/20 ip=192.168.2.20 latency=0 link=yes multicast=yes port=twisted pair speed=2.5Gbit/s
     resources: <REDACTED>
TCP test
$ iperf3 -c 192.168.2.50 —bidir

Connecting to host 192.168.2.50, port 5201
[  5] local 192.168.2.20 port 37664 connected to 192.168.2.50 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   282 MBytes  2.36 Gbits/sec    0    403 KBytes       
[  5]   1.00-2.00   sec   282 MBytes  2.36 Gbits/sec    0   1.02 MBytes       
[  5]   2.00-3.00   sec   281 MBytes  2.36 Gbits/sec    0   1.08 MBytes       
[  5]   3.00-4.00   sec   281 MBytes  2.36 Gbits/sec    0   1.08 MBytes       
[  5]   4.00-5.00   sec   280 MBytes  2.35 Gbits/sec    0   1.08 MBytes       
[  5]   5.00-6.00   sec   280 MBytes  2.35 Gbits/sec    0   1.08 MBytes       
[  5]   6.00-7.00   sec   280 MBytes  2.35 Gbits/sec    0   1.08 MBytes       
[  5]   7.00-8.00   sec   281 MBytes  2.36 Gbits/sec    0   1.08 MBytes       
[  5]   8.00-9.00   sec   280 MBytes  2.35 Gbits/sec    0   1.08 MBytes       
[  5]   9.00-10.00  sec   281 MBytes  2.36 Gbits/sec    0   1.08 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  2.74 GBytes  2.36 Gbits/sec    0             sender
[  5]   0.00-10.00  sec  2.74 GBytes  2.35 Gbits/sec                  receiver

iperf Done.
UDP test
$ iperf3 -c 192.168.2.50 -u -b 3000m —bidir

Connecting to host 192.168.2.50, port 5201
[  5] local 192.168.2.20 port 38381 connected to 192.168.2.50 port 5201
[ ID] Interval           Transfer     Bitrate         Total Datagrams
[  5]   0.00-1.00   sec   285 MBytes  2.39 Gbits/sec  206411  
[  5]   1.00-2.00   sec   285 MBytes  2.39 Gbits/sec  206424  
[  5]   2.00-3.00   sec   285 MBytes  2.39 Gbits/sec  206405  
[  5]   3.00-4.00   sec   285 MBytes  2.39 Gbits/sec  206393  
[  5]   4.00-5.00   sec   285 MBytes  2.39 Gbits/sec  206413  
[  5]   5.00-6.00   sec   285 MBytes  2.39 Gbits/sec  206369  
[  5]   6.00-7.00   sec   285 MBytes  2.39 Gbits/sec  206419  
[  5]   7.00-8.00   sec   285 MBytes  2.39 Gbits/sec  206419  
[  5]   8.00-9.00   sec   285 MBytes  2.39 Gbits/sec  206381  
[  5]   9.00-10.00  sec   285 MBytes  2.39 Gbits/sec  206396  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec  2.78 GBytes  2.39 Gbits/sec  0.000 ms  0/2064030 (0%)  sender
[  5]   0.00-10.04  sec  2.71 GBytes  2.31 Gbits/sec  0.009 ms  0/2064029 (0%)  receiver

iperf Done.

The results are on par with my expectations and I haven't had any compatibility issues with the device across different operating systems.

This article was updated on Tuesday, June 11, 2024