- Newest
- Most votes
- Most comments
Hi, using SMBv3 encryption can impact the performance. To help improve the performance, I would suggest using the SMB version 2 (vers=2.1) in mount options and changing the SMB security strategy on file gateway to either client negotiated or enforce signing. Based on your dataset and average file size, you may also consider changing the rsize and wsize to higher value up-to 16 MB.
Example entry for fstab with SMB version 2 and rsize, wsize modified.
//filegateway-ip/fileshare /mountpoint cifs rw,relatime,vers=2.1,cache=strict,username=<username>,uid=0,noforceuid,gid=0,noforcegid,addr=<filegateway-ip>,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,echo_interval=60,actimeo=1
Setting a security level for your gateway : https://docs.aws.amazon.com/filegateway/latest/files3/security-strategy.html
I would also recommend considering utility like fpsync or GNU parallel on Ubuntu client which can use multiple processes in parallel to copy to the file share. Please refer below article for instructions to enable these tools.
https://aws.amazon.com/premiumsupport/knowledge-center/efs-copy-data-in-parallel/
Hi
I tried out your suggestion of changing the SMB version., but it seems that it is actually slower now. This problem only started to appear after i migrated it to a new storage gateway. All settings stayed the same as they where on the previous storage gateway.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
Based on the mount command you shared, it appears like you are connecting to NFS file share hosted on the Storage Gateway. Is that correct?
If you are using NFS file share, the PHD message you received doesn't apply. It only applies to SMB file shares created during Jan 5 - 10.
We recommend using "hard" and "nolock" options in the mount command. Please refer to this documentation page.
https://docs.aws.amazon.com/filegateway/latest/files3/GettingStartedAccessFileShare.html
Even though it may not improve the performance, we strongly recommend including those two options. Can you please make this change and share your experience? Please share your updated mount command.
It is actually an SMB (CIFS) share, so I assume that PHD message does apply.