I am not sure I can provide you an optimal range but I can list some factors to consider. In general the guideline is to keep directories to 500K files or so. Keeping your metadata on separate NSDs, and preferably fast NSDs, helps especially with directory listings. And running the latest version of Scale also helps.
It is unclear to me why the number of files in a directory would impact remount unless these are exported directories and the remount is occurring on a user node that also attempts to scan through the directory. Fred __________________________________________________ Fred Stock | IBM Pittsburgh Lab | 720-430-8821 [email protected] From: "Michael Dutchak" <[email protected]> To: [email protected] Date: 09/11/2018 09:21 AM Subject: [gpfsug-discuss] Optimal range on inode count for a single folder Sent by: [email protected] I would like to find out what the limitation, or optimal range on inode count for a single folder is in GPFS. We have several users that have caused issues with our current files system by adding up to a million small files (1 ~ 40k) to a single directory. This causes issues during system remount where restarting the system can take excessive amounts of time. _______________________________________________ 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
