> [Excellent description of a test of Windows lazy-writes and FB/IB with
> Forced Writes = OFF]
> Wow! You've shattered my understanding/expectation of how Windows would
> flush it's cache.
Same test on Linux loses very little or no data.
> > Obviously the easiest solution is to disconnect/connect every
> > hour or so, but that seams like a bodge to me.
> (I have to ask the obvious)
> Wouldn't a better solution be to set Forced Writes = ON?
Too slow, is the simple answer. The app in question is collection a lot a
data and importing it into the database whilst performing additional
processing. With forced writes OFF it takes about 8-9 hours to import a days
data, with them ON it takes 3-4 times as long (which is longer than a day)
If I were to run two instances of the importer app, I would need to introduce
loads of table/record locking stuff, which would hardly gain me any time.
4:43pm up 34 days, 9:54, 1 user, load average: 0.74, 0.20, 0.13