Subject | Re: [ib-support] When do FB/IB 'flush' to disk? |
---|---|
Author | Ann W. Harrison |
Post date | 2001-12-04T18:46:15Z |
Paul Schmidt wrote:
hold RC2 or FB1 for it.
that Firebird has a write-back cache, not a write-through cache.
That means that pages remain in cache until they must be written,
which ordinarily means on commit. I doubt that you would see
significant difference in performance between "async on commit"
and "sync" writes.
its platform - Netware, VMS, et al.
Regards,
Ann
www.ibphoenix.com
We have answers.
>Phil Shrimpton wrote:
> > > The function is "FlushFileBuffers".
> >
> > Would this be easy to implement in Firebird (for those of us that areIt would not be very difficult, but not so easy that I want to
> > C impaired),
hold RC2 or FB1 for it.
> > and if so when should it call it, and how often.Paul Schmidt wrote:
> > The two options that come to my mind are "Every Nth Commit" or "Every
> > Nth Second"
>It would make sense to have this every commit, ... By decreasing timeErr, that's pretty much what the synch write does now. Remember
>between commits, you increase execution time, but decrease risk.
that Firebird has a write-back cache, not a write-through cache.
That means that pages remain in cache until they must be written,
which ordinarily means on commit. I doubt that you would see
significant difference in performance between "async on commit"
and "sync" writes.
>Now as for the C code, it depends on whether they use WindowsWindows. In general, the engine uses the native file handling for
>style file handling,
its platform - Netware, VMS, et al.
Regards,
Ann
www.ibphoenix.com
We have answers.