| Legal Notice Page: Clarification of Copyright Statement. Red Hat owns the copyright to this and all other subsequent derivative works. Werner Puschitz retains the copyright to the original at www.puschitz.com. | | Chapter 2, 32 bit Architecture: Added “In Red Hat Enterprise Linux 5, a 32 bit kernel is always a hugemem kernel so there is no need to install a special kernel.” | | Chapter 4, The I/O Scheduler: Added “Red Hat Enterprise Linux 5 in fact allows users to change I/O schedulers dynamically (ie echo sched_name > /sys/block/<sdx>/queue/scheduler)” | | Chapter 5, Tuning the Page Cache: Added “For Red Hat Enterprise Linux4/5, the pagecache is dynamically adjusted. You can adjust the minimum free pages using; # echo 1024 > /proc/sys/vm/min_free_kbytes Again to make the change permanent,add the following line to the file /etc/sysctl.conf; # echo vm.min_free_kbytes=1024 >> /etc/sysctl.conf Additional tuning can be done to start reclaiming pagecache pages by adjusting the swappiness percentage as described in the next section.” | | Chapter 12: Changed title to “Enabling Asynchronous I/O and Direct I/O Support | | Chapter 12, Enabling Asynchronous I/O in Oracle 9i and 10g: Added “If you use file systems instead of raw devices or ASM for data files, then you need to ensure that the datafiles reside on file systems that support asynchronous I/O (e.g., OCFS/OCFS2, ext2, ext3). To do async I/O on file systems the filesystemio_options parameter needs to be set to "asynch". Eliminated all references to disk_asynch_io=true Added “For Red Hat Enterprise Linux 3, it is recommended you use direct I/O ONLY for ext2, ext3, GFS, NFS and OCFS file systems. For Red Hat Enterprise Linux 4/5, it is strongly recommended to “setall” for ext2, ext3, GFS, NFS and OCFS file systems.” | | Chapter 14: Added Note “As explained in detail in this section, enabling big pages helps reduce TLB misses. However, this performance benefit is realized primarily when using large SGA sizes. Once a portion of memory is locked down for big pages, applications that use normal pages cannot access that portion of the memory. It is very important to make sure that there is enough memory for normal pages for applications and users to avoid excessive swapping. So, it is recommended that big pages be used only on systems that have large amounts of physical memory and for SGA sizes of 16GB or greater.” | | Chapter 18: Deleted chapter on Oracle's Orion performance prediction tool |
|
Red Hat Summit
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}