Log Buffer Space Event

Read this article: Description of common wait events for Oracle
Http://database.ctocio.com.cn/tips/38/6669538.shtml

For log buffer space-
The description is as follows:

This wait occurs when you create a redo log on a log buffer that is faster than LGWR writes or if log switch is too slow. This wait appears, usually indicates that the redo log buffer is too small, in order to solve this problem, you can consider increasing the size of the log file, or increase the size of the log buffer.

Another possible cause is a bottleneck in disk I/O, and you might consider using a disk with a faster write speed. Settings under allowed conditions consider using a bare device to hold log files and improve write efficiency. In a general system, the lowest standard is not to put log files and data files together, because usually log files are read-only, separate storage can be achieved performance gains.

I've never met a log Buffer space waiting.
But I think the previous paragraph is not reliable, the latter section is the solution.

The first paragraph can be considered to increase the size of the log file How can you solve the problem?
Like the train from Shanghai to Beijing, a lot of people crowded in Shanghai station on the platform, this solution means to expand Beijing's site? Does this solve the problem?

or increase the size of the log buffer
This is the platform to expand the Shanghai station. It seems quite reasonable, but it is not. Because there are too many rules to brush the log buffer, one of them will brush, there is a rule, 1/3 full brush.
So log buffer is a very high frequency to brush the data to the log file.

Transferred from: http://www.itpub.net/thread-1335353-1-1.html

Log Buffer space event (GO)