John Stanton wrote:
John Elrick wrote:
John Stanton wrote:
I would look at the disk controller/disk drive hardware and the
software driver to see if they are reporting correctly to the OS.
Some of your numbers are too fast for regular disk technology and
suggest that there are either hardware defects or intentional
shortcuts to always perform some form of lazy write.
Even the fastest 15,000 RPM disks will take a minimum of 8 millisecs
for a secure disk write, and it is that disk latency which is the
limiting factor in secure buffer flushing.
One performance timed example from an older machine with our application
was 128 INSERTS in 15.069 seconds. That would be 110 milliseconds per
write. The faster machine was showing about 2.0 seconds for the same
operation, or 15 milliseconds per write.
The Ruby script I posted showed 8 seconds to save 1000 rows, or just at
the edge of what you show as a minimum possibility, however it showed
115 seconds or around 115 milliseconds per write on the "slower" machine.
While I agree that 8 milliseconds is just too darn good to be true, I'm
a little hesitant to call 110 milliseconds a reasonable number for a
secure disk write. But then again, I could be wrong. I'm no expert in
low level hard drive programming, which I why I have asked for ideas
here<g>.
John
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
