LMbench2.0 results
From: Andrew Morton <[email protected]>
Quoted 7 lines
Quoted 5 lines · Paolo Ciarrocchi
Hi all,
I've just ran lmbench2.0 on my laptop.
Here the results (again, 2.5.33 seems to be "slow", I don't know why...)
Quoted 5 lines
The fork/exec/mmap slowdown is the rmap overhead. I have some stuff which partialy improves it.
The many-small-file-create slowdown is known but its cause is not. I need to get oprofile onto it.
Let me know if do something usefull for you.
Now I compiled the 2.5.33 with _NO_ preemption (the x tagged kernel). Performance are better, but it still "slow".
cd results && make summary percent 2>/dev/null | more make[1]: Entering directory `/usr/src/LMbench/results'
L M B E N C H 2 . 0 S U M M A R Y
------------------------------------
Basic system parameters
----------------------------------------------------
Host OS Description Mhz
--------- ------------- ----------------------- ----
frodo Linux 2.4.18 i686-pc-linux-gnu 797 frodo Linux 2.4.19 i686-pc-linux-gnu 797 frodo Linux 2.5.33 i686-pc-linux-gnu 797 frodo Linux 2.5.33x i686-pc-linux-gnu 797
Processor, Processes - times in microseconds - smaller is better
----------------------------------------------------------------
Host OS Mhz null null open selct sig sig fork exec sh
call I/O stat clos TCP inst hndl proc proc proc
--------- ------------- ---- ---- ---- ---- ---- ----- ---- ---- ---- ---- ----
frodo Linux 2.4.18 797 0.40 0.56 3.18 3.97 1.00 3.18 115. 1231 13.K frodo Linux 2.4.19 797 0.40 0.56 3.07 3.88 1.00 3.19 129. 1113 13.K frodo Linux 2.5.33 797 0.40 0.61 3.78 4.76 1.02 3.37 201. 1458 13.K frodo Linux 2.5.33x 797 0.40 0.60 3.51 4.38 1.02 3.27 159. 1430 13.K
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ----- ------ ------ ------ ------ ------- -------
frodo Linux 2.4.18 0.990 4.4200 13.8 6.2700 309.8 58.6 310.5 frodo Linux 2.4.19 0.900 4.2900 15.3 5.9100 309.6 57.7 309.9 frodo Linux 2.5.33 1.620 5.2800 15.3 9.3500 312.7 54.9 312.7 frodo Linux 2.5.33x 1.040 4.3200 17.8 7.6200 312.5 49.9 312.5
*Local* Communication latencies in microseconds - smaller is better
-------------------------------------------------------------------
Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP
ctxsw UNIX UDP TCP conn
--------- ------------- ----- ----- ---- ----- ----- ----- ----- ----
frodo Linux 2.4.18 0.990 4.437 8.66 frodo Linux 2.4.19 0.900 4.561 7.76 frodo Linux 2.5.33 1.620 6.497 9.11
frodo Linux 2.5.33x 1.040 4.888 8.70
File & VM system latencies in microseconds - smaller is better
--------------------------------------------------------------
Host OS 0K File 10K File Mmap Prot Page
Create Delete Create Delete Latency Fault Fault
--------- ------------- ------ ------ ------ ------ ------- ----- -----
frodo Linux 2.4.18 68.9 16.0 185.8 31.6 425.0 0.789 2.00000
frodo Linux 2.4.19 68.9 14.9 186.5 29.8 416.0 0.798 2.00000
frodo Linux 2.5.33 77.8 19.1 211.6 38.3 774.0 0.832 3.00000
frodo Linux 2.5.33x 77.2 18.8 206.7 37.0 769.0 0.823 3.00000*Local* Communication bandwidths in MB/s - bigger is better
-----------------------------------------------------------
Host OS Pipe AF TCP File Mmap Bcopy Bcopy Mem Mem
UNIX reread reread (libc) (hand) read write
--------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- -----
frodo Linux 2.4.18 810. 650. 181.7 203.7 101.5 101.4 203. 195.3 frodo Linux 2.4.19 808. 680. 187.2 203.8 101.5 101.4 203. 190.1 frodo Linux 2.5.33 571. 636. 185.6 202.5 100.5 100.4 202. 190.3 frodo Linux 2.5.33x 768. 710. 185.4 202.5 100.5 100.4 202. 189.5
Memory latencies in nanoseconds - smaller is better
(WARNING - may not be correct, check graphs)
---------------------------------------------------
Host OS Mhz L1 $ L2 $ Main mem Guesses --------- ------------- ---- ----- ------ -------- ------- frodo Linux 2.4.18 797 3.767 8.7890 158.9 frodo Linux 2.4.19 797 3.767 8.7980 158.9 frodo Linux 2.5.33 797 3.798 8.8660 160.1 frodo Linux 2.5.33x 797 3.796 45.5 160.2
make[1]: Leaving directory `/usr/src/LMbench/results'
Hope it helps.
Ciao,
Paolo
Signature · 4 lines
Get your free email from www.linuxmail.org Powered by Outblaze
Quoted 4 lines · Paolo Ciarrocchi
...
File & VM system latencies in microseconds - smaller is better
--------------------------------------------------------------
Quoted 8 lines
Host OS 0K File 10K File Mmap Prot Page
Create Delete Create Delete Latency Fault Fault
--------- ------------- ------ ------ ------ ------ ------- ----- -----
frodo Linux 2.4.18 68.9 16.0 185.8 31.6 425.0 0.789 2.00000
frodo Linux 2.4.19 68.9 14.9 186.5 29.8 416.0 0.798 2.00000
frodo Linux 2.5.33 77.8 19.1 211.6 38.3 774.0 0.832 3.00000
frodo Linux 2.5.33x 77.2 18.8 206.7 37.0 769.0 0.823 3.00000The create/delete performance is filesystem-specific.
profiling lat_fs on ext3:
c0170b70 236 0.372293 ext3_get_inode_loc c014354c 278 0.438548 __find_get_block c017cbf0 284 0.448013 journal_cancel_revoke c017ee24 291 0.459056 journal_add_journal_head c0171030 307 0.484296 ext3_do_update_inode c017856c 353 0.556861 journal_get_write_access c0178088 487 0.768248 do_get_write_access c0114744 530 0.836081 smp_apic_timer_interrupt c0178a84 559 0.881829 journal_dirty_metadata c0130644 832 1.31249 generic_file_write_nolock c0172654 2903 4.57951 ext3_add_entry c016ca10 3636 5.73583 ext3_check_dir_entry c0107048 47078 74.2661 poll_idle
ext3_check_dir_entry is just sanity checking. hmm.
on ext2:
c017f3ec 138 0.239971 ext2_free_blocks c012f560 147 0.255621 unlock_page c017f954 148 0.25736 ext2_new_block c017f2f0 154 0.267793 ext2_get_group_desc c0181958 162 0.281705 ext2_new_inode c014354c 182 0.316483 __find_get_block c0154f64 184 0.319961 __d_lookup c0109bc0 232 0.403429 apic_timer_interrupt c0143cc4 455 0.791208 __block_prepare_write c0114744 459 0.798164 smp_apic_timer_interrupt c0130644 1634 2.84139 generic_file_write_nolock c0180c64 6084 10.5796 ext2_add_link c0107048 42472 73.8554 poll_idle
This is mostly in ext2_match() - comparing strings while searching the directory. memcmp().
ext3 with hashed index directories:
c01803dc 292 0.495251 journal_unlock_journal_head c0170b70 313 0.530868 ext3_get_inode_loc c01801a4 412 0.698779 journal_add_journal_head c014354c 455 0.77171 __find_get_block c0171030 489 0.829376 ext3_do_update_inode c017df70 515 0.873474 journal_cancel_revoke c01798ec 555 0.941316 journal_get_write_access c0173208 568 0.963365 ext3_add_entry c0179408 804 1.36364 do_get_write_access c0179e04 838 1.4213 journal_dirty_metadata c0130644 1127 1.91147 generic_file_write_nolock c0107048 44117 74.8253 poll_idle
And yet the test (which tries to run for a fixed walltime) seems to do the same amount of work. No idea what's up with that.
Lessons: use an indexed-directory filesystem, and consistency checking costs.