Revisiting The Linux 6.19 Performance With "NEXT_BUDDY" Now Disabled

Written by Michael Larabel in Software on 26 January 2026 at 10:24 AM EST. Page 4 of 5. 2 Comments.

The MariaDB database benchmarks were mixed with the heavier instances regressing when dealing with 128 threads/clients but coming out faster on Linux 6.19 when having 64 threads/clients.

👁 MariaDB mariadb-slap benchmark with settings of Clients: 256. Linux 6.19 Git 23 Jan was the fastest.

MariaDB with the mariadb-slap (mysql-slap) benchmark for facilitating the testing saw a performance hit from disabling NEXT_BUDDY but still faster than where it was on Linux 6.18.

👁 PostgreSQL benchmark with settings of Scaling Factor: 100, Clients: 800, Mode: Read Write. v6.18 was the fastest.

👁 PostgreSQL benchmark with settings of Scaling Factor: 100, Clients: 800, Mode: Read Write, Average Latency. v6.18 was the fastest.

👁 PostgreSQL benchmark with settings of Scaling Factor: 100, Clients: 1000, Mode: Read Write. v6.18 was the fastest.

👁 PostgreSQL benchmark with settings of Scaling Factor: 100, Clients: 1000, Mode: Read Write, Average Latency. v6.18 was the fastest.

PostgreSQL meanwhile continued performing worse on Linux 6.19 than Linux 6.18 but disabling NEXT_BUDDY did increase the performance marginally.

👁 Stress-NG benchmark with settings of Test: Socket Activity. v6.18 was the fastest.

Disabling NEXT_BUDDY showed a clear benefit in Stress-NG's socket activity micro-benchmark. However, the performance remained slower than on Linux 6.18 stable.

2 Comments - Next Page

Page: 1 2 3 4 5 Next Page

URL: https://www.phoronix.com/review/linux-619-next-buddy/4

⇱ Revisiting The Linux 6.19 Performance With "NEXT_BUDDY" Now Disabled Review - Phoronix

Revisiting The Linux 6.19 Performance With "NEXT_BUDDY" Now Disabled