[gpfsug-discuss] Inode scan optimization - (Tomasz.Wolski at ts.fujitsu.com )
Marc A Kaplan
makaplan at us.ibm.com
Thu Feb 8 15:33:13 GMT 2018
Please clarify and elaborate .... When you write "a full backup ... takes
60 days" - that seems very poor indeed.
BUT you haven't stated how much data is being copied to what kind of
backup media nor how much equipment or what types you are using... Nor
which backup software...
We have Spectrum Scale installation doing nightly backups of huge file
systems using the mmbackup command with TivoliStorageManager backup, using
IBM branded or approved equipment and software.
From: "Tomasz.Wolski at ts.fujitsu.com" <Tomasz.Wolski at ts.fujitsu.com>
To: "gpfsug-discuss at spectrumscale.org"
<gpfsug-discuss at spectrumscale.org>
Date: 02/08/2018 05:50 AM
Subject: [gpfsug-discuss] Inode scan optimization
Sent by: gpfsug-discuss-bounces at spectrumscale.org
Hello All,
A full backup of an 2 billion inodes spectrum scale file system on
V4.1.1.16 takes 60 days.
We try to optimize and using inode scans seems to improve, even when we
are using a directory scan and the inode scan just for having a better
performance concerning stat (using gpfs_stat_inode_with_xattrs64). With 20
processes in parallel doing dir scans (+ inode scans for stat info) we
have decreased the time to 40 days.
All NSDs are dataAndMetadata type.
I have the following questions:
· Is there a way to increase the inode scan cache (we may use 32
GByte)?
o Can we us the “hidden” config parameters
§ iscanPrefetchAggressiveness 2
§ iscanPrefetchDepth 0
§ iscanPrefetchThreadsPerNode 0
· Is there a documentation concerning cache behavior?
o if no, is the inode scan cache process or node specific?
o Is there a suggestion to optimize the termIno parameter in the
gpfs_stat_inode_with_xattrs64() in such a use case?
Thanks!
Best regards,
Tomasz Wolski_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=cvpnBBH0j41aQy0RPiG2xRL_M8mTc1izuQD3_PmtjZ8&m=mWxVB2lS_snDiYR4E348tnzbQTSuuWSrRiBDhJPjyh8&s=FG9fDxbmiCuSh0cvt4hsQS0bKdGHjI7loVGEKO0eTf0&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180208/c98ecf03/attachment-0002.htm>
More information about the gpfsug-discuss
mailing list