The ORACLE tutorial is: Oracle performance optimization. We have reason to believe that the adoption of the new kernel version (2.2.16-3 smp) should also improve the performance:
OS2: Newer minor version kernel TPC Results
Load Time (second) 9.40
Transactions/Second 11.522
At present, the kernel version 2.4 is available. Compared with the kernel version 2.2, the performance has been greatly improved. We use 2.4.1 smp:
OS3: Newer major version kernel TPC Results
Load Time (second) 8.32
Transactions/Second 12.815
In Linux, the last read time is updated during the default read operation, but this is not important to us. Therefore, we disable this option and set the noatime file attribute. (Windows NT and 2000 have similar settings)
If we only set the data file relative to Oracle, our command is
Chattr + A file_name
Implementation of the entire directory: chattr-R + A directory_name
The best way is to modify/etc/fstab and add the noatime keyword for each file system entry.
OS4: noatime file attribute
TPC Results
Load Time (second) 5.58
Transactions/Second 13.884
Another way to adjust Linux I/O is to adjust the virtual memory subsystem. Modify the/ect/sysctl. cong file and add the following line:
Vm. bdflush = 100 1200 128 512 15 5000 500 2
According to/usr/src/Linux/Documentation/sysctl/vm.txt:
The first parameter 100%: controls the maximum dirty buffer data in the buffer. Adding this value means that Linux can delay disk writing.
The second parameter 1200 ndirty indicates the maximum dirty buffer that can be written to the disk once by bdflush.
The third parameter 128 nrefill: Maximum number of buffers added to the free buffer zone by bdflush when refill_freelist () is called.
Refill_freelist () 512: When this number exceeds the nref_dirt dirty buffer, bdflush is awakened.
The fifth and last two parameters are 1884 and 2. The system is not used and we will not modify them.
Age_buffer 50 * HZ, age_super parameter 5 * HZ: control the maximum wait time for Linux to write dirty buffer to the disk. The value is represented by the number of calls (jiffies), which is 100 jiffies per second.
OS5: bdflush settings TPC Results
Load Time (second) 4.43
Transactions/Second 14.988
After the above adjustments, the final loading time is reduced by 1015.35% and TPS is increased by 45.61%.