Intel FRED Can Yield Greater Performance - FRED Benchmarks On Panther Lake

Written by Michael Larabel in Processors on 23 March 2026 at 11:20 AM EDT. Page 2 of 6. 14 Comments.

👁 Flexible IO Tester benchmark with settings of Type: Random Read, Engine: IO_uring, Direct: No, Block Size: 4KB, Job Count: 8, Disk Target: Default Test Directory. fred=on was the fastest.

👁 Flexible IO Tester benchmark with settings of Type: Random Read, Engine: IO_uring, Direct: No, Block Size: 4KB, Job Count: 16, Disk Target: Default Test Directory. fred=on was the fastest.

First up was hitting the Intel Panther Lake system with the FIO benchmark for exercising the Micron 2500 MTFDKBA1T0QGN NVMe SSD with this MSI Prestige 14 Flip AI+ laptop in knowing that FRED should be of particular benefit to heavy I/O usage.

👁 Flexible IO Tester benchmark with settings of Type: Random Write, Engine: IO_uring, Direct: No, Block Size: 4KB, Job Count: 8, Disk Target: Default Test Directory. fred=on was the fastest.

👁 Flexible IO Tester benchmark with settings of Type: Random Write, Engine: IO_uring, Direct: No, Block Size: 4KB, Job Count: 16, Disk Target: Default Test Directory. fred=on was the fastest.

👁 Flexible IO Tester benchmark with settings of Type: Random Write, Engine: IO_uring, Direct: Yes, Block Size: 4KB, Job Count: 8, Disk Target: Default Test Directory. fred=on was the fastest.

Sure enough, FRED really delivers! When it's enabled...

👁 Flexible IO Tester benchmark with settings of Type: Random Write, Engine: IO_uring, Direct: Yes, Block Size: 4KB, Job Count: 16, Disk Target: Default Test Directory. fred=on was the fastest.

The random write performance in particular saw some huge gains with FRED enabled on Intel Panther Lake.

👁 Flexible IO Tester benchmark with settings of Type: Sequential Read, Engine: IO_uring, Direct: Yes, Block Size: 2MB, Job Count: 8, Disk Target: Default Test Directory. fred=on was the fastest.

👁 Flexible IO Tester benchmark with settings of Type: Sequential Write, Engine: IO_uring, Direct: No, Block Size: 2MB, Job Count: 8, Disk Target: Default Test Directory. fred=on was the fastest.

👁 Flexible IO Tester benchmark with settings of Type: Sequential Write, Engine: IO_uring, Direct: Yes, Block Size: 2MB, Job Count: 8, Disk Target: Default Test Directory. fred=on was the fastest.

👁 Flexible IO Tester benchmark with settings of Type: Sequential Write, Engine: IO_uring, Direct: Yes, Block Size: 2MB, Job Count: 16, Disk Target: Default Test Directory. fred=on was the fastest.

For sequential reads the gains were small but when turning to FIO sequential writes were again some very dramatic improvements with FRED enabled. Again leaving me really surprised that FRED isn't enabled by default on the Linux kernel at this time and seeing no clear communication why.

14 Comments - Next Page

Page: 1 2 3 4 5 6 Next Page

URL: https://www.phoronix.com/review/intel-fred-panther-lake/2

⇱ Intel FRED Can Yield Greater Performance - FRED Benchmarks On Panther Lake Review - Phoronix

Intel FRED Can Yield Greater Performance - FRED Benchmarks On Panther Lake