Subject | GBAK processing |
---|---|
Author | Leyne, Sean |
Post date | 2000-04-26T17:24:56Z |
Is GBAK (the backup process) a single threaded function, performing 1
task at a time, or is it multi-threaded?
Since I think the answer is that it is single threaded, I'll ask a
couple of other questions.
Would a multi-threaded backup process perform faster then the current
model?
What issue would prevent (or made very difficult) GBAK being made
multi-threaded?
I been thinking about a different approach to GBAK where it creates
treads (up to a certain limit) for each DB object to be backed up, with
these threads reading the DB information and building "backup
information" to be written out by a single "writer thread". I
understand that the system structure would need to be processed by a
single thread and written to disk before any application data.
Sean
task at a time, or is it multi-threaded?
Since I think the answer is that it is single threaded, I'll ask a
couple of other questions.
Would a multi-threaded backup process perform faster then the current
model?
What issue would prevent (or made very difficult) GBAK being made
multi-threaded?
I been thinking about a different approach to GBAK where it creates
treads (up to a certain limit) for each DB object to be backed up, with
these threads reading the DB information and building "backup
information" to be written out by a single "writer thread". I
understand that the system structure would need to be processed by a
single thread and written to disk before any application data.
Sean