Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Derek Martin wrote: > The reason I didn't do this (I didn't know how, but it did occur to me > it was probably possible, and google would tell me) is because I > figured it was a bit unfair... though actually, it might make for a > more accurate test, in some sense. Real world case vs. synthetic benchmark. I don't actually know whether or not it will make a difference. I do know that having cached data or fragmented memory from a prior run that isn't flushed by the dd trick can have an effect. Better to start with a clean slate for each run. Better still to run each test after a clean reboot. If you want to be really picky about it, run the test on file systems mounted sync,dirsync. Get kernel write buffering out of the picture. -- Rich P.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |