[Samba] vfs readahead && windows server 2016/2019?
jra at samba.org
Tue Nov 10 01:06:05 UTC 2020
On Mon, Nov 09, 2020 at 07:26:13PM -0500, Robert Buck wrote:
> Hi Jeremy, thank you for your very helpful response. We're looking at a few
> more options. Would you have the time to provide some guidance on these,
> how helpful they may be?
The man pages you're pointing to here are obsolete. All
accurate information is now in the wiki.
> - *aio ** ->
Obsolete. All reads/writes should now be done via the pthreadpool. Or
> - *write cache* ->
Obsolete and code now removed.
> - *vfs_cacheprime *
Obsolete. Let the kernel do its thing.
> - *vfs_full_audit*
All audit code will slow things down :-).
> If you were to rank the likelihood of these helping, how would you rank
> them? Are they still applicable in modern Windows and RHEL?
> Our top challenge right now is Windows Explorer, specifically when you get
> properties on a directory, it takes very long to provide a file count, etc,
> comparatively to a share from another Windows Server.
> We just moved all CTDB volatile persistent state to NVMe and we have not
> tested the impact yet, and this may prove significantly beneficial. So the
> Windows Explorer issues may prove to be solved during tomorrow's testing.
> And we're also planning on testing turning off locking in the root folder
> this week, as we've been told this can help a lot too.
> Bear in mind, we are likely to have upwards of 500-800 concurrent users per
> share. We're running in AWS, for both Samba servers and Windows Server
> (desktop streaming).
The meta-data being fetched on directory read is seems like what
is causing problems. Funding Samba to add directory leasing code
will probably help greatly here.
More information about the samba