Subject | Re: [Firebird-Architect] Group Commits |
---|---|
Author | Dmitry Yemanov |
Post date | 2004-11-08T06:31:09Z |
"Jim Starkey" <jas@...> wrote:
Got it, thx.
Can we suppose scenarios when even 20-50 ms delay on commit is unacceptable?
If so, may I suggest that a zero config option means no group commit? Or
perhaps we may introduce isc_tpb_no_group_commit causing transaction to
flush its buffers immediately?
Do you want to reuse the cache writer thread for this purpose or add a new
one?
Dmitry
>operations.
> I'll try it again. A call to isc_commit_transaction waits until the
> next group commit cycle. On average, it will incur a cycle/2 latency.
> This must be balanced against the system cost of avoidable write
Got it, thx.
Can we suppose scenarios when even 20-50 ms delay on commit is unacceptable?
If so, may I suggest that a zero config option means no group commit? Or
perhaps we may introduce isc_tpb_no_group_commit causing transaction to
flush its buffers immediately?
Do you want to reuse the cache writer thread for this purpose or add a new
one?
Dmitry