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
