Rich,

I got the point: with forced writes off you can't be sure of when the data is sent to disk.
But, in that case, what is the point of turning it off ? If you must wait for the server shut down to be 100% sure that the data is written to disk, isn't the risk too high to have forced write off ?
I suspect that data is written to disk far before than the server shut down or a connection close, otherwise FB designers shoudn't leave forced write as an option, it should always be activated.

Aldo
 

 

On 2014-08-18 14:51, Aldo Caruso aldo.caruso@...
[firebird-support] wrote:
> After that I noticed that some massive updates ( 100K records ) took
> nearly 5 minutes, whereas with async writes it used to take 10 seconds.

Of course, we don't know how much work actually took place during that
10 second period when
forced writes were off. Could be that very little of the update was
actually on disk
at that point. So do you consider the massive update actually done at
that point?

Also while forced writes are off, when is all that "5 minutes" worth of
work actually done? When the database is closed? When the server was
shut down? Thats's the problem with forced writes being off - you never
know.

--

Cheers!
Rich Saunders