redo log buffer using [message #509448] |
Fri, 27 May 2011 16:09 |
|
Karlia
Messages: 40 Registered: May 2011 Location: Algiers
|
Member |
|
|
Hi every body,
I learnt that logWriter writes in the redo log files when redo log buffer is 1/3 full,
it means that 66 % of redo log buffer are always empty and never used,
am i mistaken ?
if no, isn't a waste of memory (66 % always empty !)
thanks to every body
|
|
|
Re: redo log buffer using [message #509449 is a reply to message #509448] |
Fri, 27 May 2011 16:25 |
John Watson
Messages: 8960 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
You might have a thousand server processes writing to the log buffer, in memory. You have one log writer writing the log buffer to files, on disc. Which is faster, writing to memory or to disc? It is more than likely that at times of high activity you will be generating redo faster than it can be written to disc. That is why log writer starts writing before the buffer is full. If the buffer fills, the entire instance will hang.
Does that help?
|
|
|
|
Re: redo log buffer using [message #509460 is a reply to message #509459] |
Sat, 28 May 2011 01:04 |
Yasir Hashmi
Messages: 304 Registered: April 2006
|
Senior Member |
|
|
Similarly,DBWR wakes up after every 3 secs to see if there are any dirty buffers to write to disk.
BUt it is slow than LGWR as DBWR writes blocks and LGWR write bytes.So you might have seen checkpoint not complete message in the alert log due to that reason.
|
|
|
|
|