![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
For DB2 Version 9.5, does setting swappiness= 0 (/proc/sys/vm/swappiness) on RHEL 5 sufficiently limit Linux file system caching, or is there some other way to limit on the percent of memory that can be used for Linux file system caching. |
#3
| |||
| |||
|
|
Mark A wrote: For DB2 Version 9.5, does setting swappiness= 0 (/proc/sys/vm/swappiness) on RHEL 5 sufficiently limit Linux file system caching, or is there some other way to limit on the percent of memory that can be used for Linux file system caching. My completely non-authoritative answer would be: The vm.swappiness parameter is irrelevant here. |
#4
| |||
| |||
|
|
My completely non-authoritative answer would be: The vm.swappiness parameter is irrelevant here. To prevent file system caching, DB2 will use relevant file system API hooks to instruct the kernel to skip caching of reads and writes. DB2 probably uses the O_DIRECT flag when opening the involved data files; or perhaps IBM has listened to Linus Torvalds and uses other API facilities: http://kerneltrap.org/node/7563 -- Troels |
#5
| |||
| |||
|
|
I don't think that this is irrelevant. There are many other files on the system accessed outside of DB2. A simple daily cron job calling updatedb can wreak havoc, sucking memory into the file system cache. |
![]() |
| Thread Tools | |
| Display Modes | |
| |