Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1354232
  • 博文数量: 239
  • 博客积分: 5909
  • 博客等级: 大校
  • 技术积分: 2715
  • 用 户 组: 普通用户
  • 注册时间: 2010-07-24 20:19
文章分类

全部博文(239)

文章存档

2014年(4)

2013年(22)

2012年(140)

2011年(14)

2010年(59)

我的朋友

分类: Oracle

2012-10-30 18:14:09


点击(此处)折叠或打开

  1. log sync waits are most commonly caused by frequent commits. When you commit, you must
  2. wait for LGWR to flush the contents of the redo log buffer to disk (else we could not
  3. assure you of recovery).

  4. A small log buffer would manifest itself as a LOG_BUFFER_SPACE wait.

  5. Having data files and other things on the same device as your online redo log can
  6. definitely impact log writers ability to do its job as fast as possible.

  7. Things you can do:

  8. o look at your transactions. If you are "over committing" -- commiting in the mistaken
  9. belief that you are saving resources and not on true transactional boundaries -- stop it.
  10. Commit only when your transaction is over and do not commit too frequently (if you have
  11. very small transactions, so be it -- you MUST commit but if you are committing just for
  12. the sake of committing, don't)

  13. o speed up LGWR. Make it more efficient. Ensure you are not using something like RAID 5
  14. for log devices. Reduce contention on that device (let LGWR own it). Ensure LGWR and
  15. ARCH are not contending with eachother (you want at lead 5 devices dedicated to logging
  16. -- you NEED to mirror redo members and you NEED to archive. So, if you have disks 1..5
  17. you can:

  18. have redo log groups 1, 3, 5, 7, .... on disks 1 and 3
  19. redo log groups 2, 4, 6, 8, .... on disks 2 and 4
  20. archive destination to disk 5

  21. Now, when LGWR is writing to groups 1, 3, 5, 7, .... on disks 1/3, ARCH will be reading
  22. groups 2, 4, 6, 8, ... on disks 2/4 and writing to disk 5. When LGWR advances, so does
  23. ARCH and they'll switch disks. Never does ARCH and LGWR contend with eachother.

In fact, you should get rid of all (or most) factors affecting redo log contention. In addition, maybe: - Making sure DBWR checkpoiting and ARCH copying are not blocking log switches (check out ALTER.LOG); - You can also verify that the following statistics in V$SYSSTAT are either high or increasing: "redo buffer allocation retries" - Total number of retries necessary to allocate space in the redo buffer. Retries are needed either because the redo writer has fallen behind or because an event such as a log switch is occurring. "redo log space requests" - Number of times the active log file is full and Oracle must wait for disk space to be allocated for the redo log entries. Such space is created by performing a log switch. In these cases, you can try some things, the main ones being: . Make DBWR more infrequent (performance will inscrease but recoverbility could be compomised). Do that adjusting FAST_START_IO_TARGET (8i) or FAST_START_MTTR_TARGET (9i). . Enlarge your redo files. This will make checkpoiting more infrequent on log switches. . Spawn more DBRWs, ARCHs, or their IO Slaves to increase throughput.



Now - now you'll be waiting for lgwr to finish writing after each record. You'll have tons of log file sync waits (like 1,000,000 of them). And if you have high log file parallel write waits - you might be able to blame part of that on the writes.
I would blame the programmer, but you could blame the IO. the IO isn't really the cause, the algorithm is, but you see what I mean.
Make sense?
log file parallel write is something lgwr waits for.

log file sync waits might be you waiting on lgwr (might be starved for CPU, lgwr might not be the cause at all). If you are waiting on lgwr, you might want to look at what lgwr is waiting for. those could be log file parallel writes.



转自:
阅读(1662) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~