[gpfsug-discuss] advanced filecache math

2019-05-09 Thread Stijn De Weirdt
hi all, we are looking into some memory issues with gpfs 5.0.2.2, and found following in mmfsadm dump fs: > fileCacheLimit 100 desired 100 ... > fileCacheMem 38359956 k = 11718554 * 3352 bytes (inode size 512 + > 2840) the limit is 1M (we configured that), however,

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Achim Rehor
Hi Stijn,you just misinterpreted the term fileCacheLimit.This is not in byte, but specifies the maxFilesToCache setting :  UMALLOC limits:    bufferDescLimit      4 desired    4    fileCacheLimit        4000 desired     4000   <=== mFtC     statCacheLimit        1000 desired     1000  

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Stijn De Weirdt
hi achim, > you just misinterpreted the term fileCacheLimit. > This is not in byte, but specifies the maxFilesToCache setting : i understand that, but how does the fileCacheLimit relate to the fileCacheMem number? (we have a 32GB pagepool, and mmfsd is using 80GB RES (101 VIRT), so we are

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Stijn De Weirdt
seems like we are suffering from http://www-01.ibm.com/support/docview.wss?uid=isg1IJ12737 as these are ces nodes, we susepcted something wrong the caches, but it looks like a memleak instead. sorry for the noise (as usual you find the solution right after sending the mail ;) stijn On 5/9/19

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Jim Doherty
A couple of observations on memory,   a maxFilesToCache object takes anwhere from 6-10K, so 1 million =~ 6-10 Gig.    Memory utilized in the mmfsd comes from either the pagepool,  the shared memory segment used by MFTC objects,  the token memory segment used to track MFTC objects,   and newer

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Anderson Ferreira Nobre
Perhaps this presentation can help you: https://pt.slideshare.net/tomerperry/ibm-spectrum-scale-memory-usage   Abraços / Regards / Saludos,   Anderson Nobre

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Achim Rehor
Sorry for my fast ( and not well thought) answer, before. You obviously are correct, there is no relation between the setting of maxFilesToCache, and the fileCacheMem     38359956 k  = 11718554 * 3352 bytes (inode size 512 + 2840)usage. it is rather a statement of how many metadata may fit in the

Re: [gpfsug-discuss] advanced filecache math

2019-05-09 Thread Sven Oehme
Unfortunate more complicated :) The consumption here is an estimate based on 512b inodes, which no newly created filesystem has as all new default to 4k. So if you have 4k inodes you could easily need 2x of the estimated value. Then there are extended attributes, also not added here, etc . So