9fans archive / 2006 / 09 / 307    prev next


    search terms are split using tokenize    
    from:regexp searches From: lines    
    subject:regexp searches Subject: lines    
    before:yyyy[/mm[/dd]] and after:yyyy[/mm[/dd]] specify date range    

    powered by grep(1)    
From: erik quanstrom <quanstro@qua...>
Subject: venti+fossil problems on new install
Date: Thu, 21 Sep 2006 18:59:39 -0500

here's another interesting performance result that i don't understand:

	ladd# ls -l shot.img
	ladd# time rc -c '{for(i in `{seq 1 100}) cat shot.img}>/dev/null' & time rc -c '{for(i in `{seq 1 100}) cat shot.img}>/dev/null' 
	0.04u 0.82s 36.07r 	 rc -c {for(i in `{seq 1 100}) cat shot.img}>/dev/null
	--rw-rw-r-- M 59 quanstro quanstro 5242940 Jul 22 13:56 shot.img
	ladd# time rc -c '{for(i in `{seq 1 100}) cat shot.img}>/dev/null' & time rc -c '{for(i in `{seq 1 100}) cat shot.img}>/dev/null' 
	0.04u 1.65s 37.82r 	 rc -c {for(i in `{seq 1 100}) cat shot.img}>/dev/null
	0.02u 1.34s 37.83r 	 rc -c {for(i in `{seq 1 100}) cat shot.img}>/dev/null
	
wall clock time was 38s. this works out 14MB/s and 14MB/s*2.  that is, neither the network
card nor my slow fs can be the bottleneck.  even 28MB/s is only 228Mbit/sec, so we're not close
to the network bandwidth. could something be rate limiting itself at a close to
100Mbit/sec per connection?

- erik