On Sun, May 20, 2012 at 01:26:48PM +0000, Black, Michael (IS) scratched on the wall: > Hmmm...our math is a bit different...
Yeah, your math is wrong... 8-) > A 1,000 RPM disk would take 1ms to spin around once A 1,000 RPS disk would, but not a 1,000 RPM disk. > I believe my original point stands...if your fsync() does nothing > you'll see something close to zero all the time. Agreed. I only meant to point out that when we're taking about physical I/O and spinning disks, "something close to zero" is measured in milliseconds, not fractions of a millisecond. If the OS is attempting to do the right thing, but the disk controller is lying about flushing the hardware cache, then you're likely to see something on the order of a millisecond or two. In that case you need to communicate all the way out to the storage device, but it isn't doing anything. If you're actually writing data to a spinning disk, I would expect times to be varied, and average out to slightly more than half a rotation. And rotations still take a LONG time in modern computing terms. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
