samba - Mar 2016 - static vs shared modules build

Since all my Samba AD member servers rely on vfs_acl_xattr to take care 
of Windows permissions, is there any performance advantage to building 
samba with a static vfs_acl_xattr module?

(./configure --with-static-modules=vfs_acl_xattr)

Thank you

Am 12.03.2016 um 19:48 schrieb Miguel Medalha:
> Since all my Samba AD member servers rely on vfs_acl_xattr to take care
> of Windows permissions, is there any performance advantage to building
> samba with a static vfs_acl_xattr module?
>
> (./configure --with-static-modules=vfs_acl_xattr)
no, it only has a theoretical impact on the number of open filehandles, 
theroretical means in that context surely not relevant for a fileserver

if you have a preforking service and expect many thousand forkers than 
it may become relevant

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20160312/403fc0c5/signature.sig>

> no, it only has a theoretical impact on the number of open 
> filehandles, theroretical means in that context surely not relevant 
> for a fileserver
>
> if you have a preforking service and expect many thousand forkers than 
> it may become relevant
Thank you

Would you give the same advice in the case of a Samba 4 AD Domain 
Controller?