 | | | -none- | -none- 2007-10-02 - By qihua wu
Back
Our database is running on hpux on which AIO is not possible to
achieve(except use raw device which is out of our considertion). And the "log
file parallel write" is very high. Since we use two redo groups to mutliplex
the redo files, and the files can only be written sequentially. So I figure
out an idea to use one group of online redo log which are mirrored. If it is
mirrored, the redo log will be written in parallel which can reduce the wait
time.
Do you think this method is feasible and what's the disadvanatge?
Our database is running on hpux on which AIO is not possible to achieve(except
use raw device which is out of our considertion). And the "<span style=
"background: yellow none repeat scroll 0% 50%; font-size: 8pt; font-family:
Arial; color: black; -moz-background-clip: -moz-initial; -moz-background-origin
: -moz-initial; -moz-background-inline-policy: -moz-initial;">
log file parallel
write" </span>is very high. Since we use two redo groups to mutliplex the
redo files, and the files can only be written sequentially. So I figure out an
idea to use one group of online redo log which are mirrored. If it is mirrored,
the redo log will be written in parallel which can reduce the wait time.
<br><br>Do you think this method is feasible and what's the disadvanatge?
<br><span style="background: yellow none repeat scroll 0%; font-size: 8pt; font
-family: Arial; color: black; -moz-background-clip: -moz-initial; -moz
-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
</span>
|
|
|