What is the purpose of file system caching while creating a tablespace?
Memory on the test server gets used up pretty quickly after a user
executes a complex query(database is already activated), after some
investgation i found out that most of it being consumed by filesystem
caching... thanks to Liam and Phil Sherman for their valuable
suggestions. Is it safe to turn off filesystem caching on every
tablespaceon the server?? or can we set DB2_MMPAP_READ=ON and
DB2_MMAP_WRITE=ON ?? what is the down side of it?? We do have a big
enough bufferpool...
---------------------------------------------------------------------------------------------------------------------------------------
vmstat -v
2097152 memory pages
1982466 lruable pages
862 free pages
1 memory pools
130485 pinned pages
80.1 maxpin percentage
20.0 minperm percentage
80.0 maxperm percentage
37.7 numperm percentage
747627 file pages
0.0 compressed percentage
0 compressed pages
0.0 numclient percentage
80.0 maxclient percentage
0 client pages
0 remote pageouts scheduled
0 pending disk I/Os blocked with no pbuf
1199107 paging space I/Os blocked with no psbuf
1744312 filesystem I/Os blocked with no fsbuf
0 client filesystem I/Os blocked with no fsbuf
0 external pager filesystem I/Os blocked with no
fsbuf
---------------------------------------------------------------------------------------------------------------------------------------
Thanks,
Raj
| 
