you just misinterpreted the term fileCacheLimit.
This is not in byte, but specifies the maxFilesToCache setting :
UMALLOC limits:
bufferDescLimit 40000 desired 40000
fileCacheLimit 4000 desired 4000 <=== mFtC
statCacheLimit 1000 desired 1000 <=== mSC
diskAddrBuffLimit 200 desired 200
# mmfsadm dump config | grep -E "maxFilesToCache|maxStatCache"
maxFilesToCache 4000
maxStatCache 1000
Mit freundlichen Grüßen / Kind regards
Achim Rehor
| Software Technical Support Specialist AIX/ Emea HPC Support | |||
| IBM Certified Advanced Technical Expert - Power Systems with AIX | |||
| TSCC Software Service, Dept. 7922 | |||
| Global Technology Services | |||
| Phone: | +49-7034-274-7862 | IBM Deutschland | |
| E-Mail: | [email protected] | Am Weiher 24 | |
| 65451 Kelsterbach | |||
| Germany | |||
| IBM
Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Martin Hartmann (Vorsitzender), Norbert Janzen, Stefan Lutz, Nicole Reimer, Dr. Klaus Seifert, Wolfgang Wendt Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 14562 WEEE-Reg.-Nr. DE 99369940 | |||
From:
Stijn De Weirdt <[email protected]>
To:
gpfsug main discussion
list <[email protected]>
Date:
09/05/2019 16:21
Subject:
[gpfsug-discuss]
advanced filecache math
Sent by:
[email protected]
hi all,
we are looking into some memory issues with gpfs 5.0.2.2, and found
following in mmfsadm dump fs:
> fileCacheLimit 1000000 desired 1000000
...
> fileCacheMem 38359956 k = 11718554 * 3352 bytes (inode size 512 + 2840)
the limit is 1M (we configured that), however, the fileCacheMem mentions
11.7M?
this is also reported right after a mmshutdown/startup.
how do these 2 relate (again?)?
mnay thanks,
stijn
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
