| commit | 20075e6b3082939fbd5d7ca4f327d29d62c33c87 | |
| author | Ralph Boehme <slow@samba.org> | |
| Wed, 1 Jul 2015 15:57:36 +0000 (1 17:57 +0200) | ||
| committer | Jeremy Allison <jra@samba.org> | |
| Wed, 1 Jul 2015 21:05:55 +0000 (1 23:05 +0200) | ||
| tree | b2dde1e110523e8b2e9a98691721437f15efbcd9 | treesnapshot (tar.gz zip) |
| parent | 4e28dd16c528e3bf3cfa0a4ecfdee9188f02ec49 | commitdiff |
s3:vfs: copy_chunk buffer size
Use a dynamically allocated copy_chunk buffer size with an upper bound
of 8 MB for now.
The previous size of 64 KB has proven to really hurt performance,
especially with "strict locking = yes".
The SMB2 protocol level maximum allowed copy_chunk size is 1 MB, that's
what will be used as buffer size in the typical case.
With the AAPL copyfile extension the requested copy_chunk size is the
size whole file, which would then make use of a larger buffer up to the
limit of 8 MB.
Signed-off-by: Ralph Boehme <slow@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
Use a dynamically allocated copy_chunk buffer size with an upper bound
of 8 MB for now.
The previous size of 64 KB has proven to really hurt performance,
especially with "strict locking = yes".
The SMB2 protocol level maximum allowed copy_chunk size is 1 MB, that's
what will be used as buffer size in the typical case.
With the AAPL copyfile extension the requested copy_chunk size is the
size whole file, which would then make use of a larger buffer up to the
limit of 8 MB.
Signed-off-by: Ralph Boehme <slow@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
| source3/modules/vfs_default.c | diffblobblamehistory |