[lkml]   [2000]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectUP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
I performed the following tests running both 2.4.0-test12-pre7 and
2.2.18-pre26. All kernel builds were done in console mode (no X).

All numbers are seconds required to make bzImage. Times were
obtained using the date command before and after make bzImage in
a script. Each test was performed three times.

1 2 3 ave.

449 443 440 444 make bzImage for 2.4.0t12p7 running 2.2.18p26
460 458 454 457.3 make bzImage for 2.4.0t12p7 running 2.4.0t12p7

310 310 307 309 make bzImage for 2.2.18p26 running 2.2.18p26
318 319 317 318 make bzImage for 2.2.18p26 running 2.4.0t12p7

2.2.18p26 is shorthand for 2.2.18-pre26.
2.4.0t12p7 is shorthand for 2.4.0-test12-pre7.

2.2.18-pre26 was patched with reiserfs-3.5.28.
2.2.18-pre26 was compiled with gcc 2.91.66 (kgcc).

2.4.0-test12-pre7 was patched with reiserfs-3.6.22.
2.4.0-test12-pre7 was compiled with gcc 2.95.3.

The .config files were unchanged during the tests.
A make clean was performed before each test.
The test machine was not connected to a network during the tests.
Test machine: single processor P-III (450 Mhz), 192MB, IDE disk (ST317221A).

Conclusion: UP 2.2.18 makes kernels 3% faster than UP 2.4.0-test12
using ReiserFS. However, the margin of victory is small enough that a
recount may be necessary.

It would be interesting to see results using ext2fs and results from SMP

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.095 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site