vfs.nfs.iothreads - how much is safe?

2023-05-12 Thread Maksim Rodin
Hello, I found an option while reading man mount_nfs: "Use sysctl(8) or modify sysctl.conf(5) to adjust the vfs.nfs.iothreads value, which is the number of kernel threads created to serve asynchronous NFS I/O requests." I tried to raise this value to a maximum of 20 and saw a dece

Re: vfs.nfs.iothreads

2013-01-05 Thread Jan Stary
To adjust the number of kernel nfsio threads used to service asynchronous I/O requests on an NFS _client_ machine. Your diff seems to imply that this affects the _server_. However, on the client, vfs.nfs.iothreads jumps to 4 as soon as I mount the NFS share. On the server

Re: vfs.nfs.iothreads

2013-01-05 Thread Jason McIntyre
On Sat, Jan 05, 2013 at 10:17:49AM +0100, Jan Stary wrote: vfs.nfs.iothreads is still mentioned (and commented out) in the default /etc/sysctl.conf - should that go too? not neccessarily. but the value should be changed, i think (or it should be removed). i've not documented the fact

Re: vfs.nfs.iothreads

2013-01-05 Thread Jan Stary
On Jan 05 14:35:40, j...@kerhand.co.uk wrote: i hope the diff committed is clear about that: NFS_NIOTHREADS The number of I/O kernel threads for NFS clients. Silly me, I was reading the old version. Yes, this is clear of course.

Re: vfs.nfs.iothreads

2013-01-03 Thread Jason McIntyre
used to service asynchronous I/O requests on an NFS _client_ machine. Your diff seems to imply that this affects the _server_. However, on the client, vfs.nfs.iothreads jumps to 4 as soon as I mount the NFS share. On the server, it stays at -1. On the client, when I start copying

Re: vfs.nfs.iothreads

2012-12-23 Thread Jason McIntyre
On Fri, Dec 21, 2012 at 02:34:50PM +0100, Jan Stary wrote: On 5.2/i386, man sysctl says To adjust the number of kernel nfsio threads used to service asynchronous I/O requests on an NFS client machine: # sysctl vfs.nfs.iothreads=4 The default is 4; 20

Re: vfs.nfs.iothreads

2012-12-23 Thread Jan Stary
vfs.nfs.iothreads=4 The default is 4; 20 is the maximum. See nfssvc(2) and nfsd(8) for further discussion. Does it still apply? The default now seems to be # sysctl vfs.nfs.iothreads vfs.nfs.iothreads=-1 which scales itself to 4 when I copy a file from

Re: vfs.nfs.iothreads

2012-12-23 Thread Jason McIntyre
machine. Your diff seems to imply that this affects the _server_. However, on the client, vfs.nfs.iothreads jumps to 4 as soon as I mount the NFS share. On the server, it stays at -1. On the client, when I start copying from the server, it stays at 4; on the server it stays at -1. Same

vfs.nfs.iothreads

2012-12-21 Thread Jan Stary
On 5.2/i386, man sysctl says To adjust the number of kernel nfsio threads used to service asynchronous I/O requests on an NFS client machine: # sysctl vfs.nfs.iothreads=4 The default is 4; 20 is the maximum. See nfssvc(2) and nfsd(8) for further discussion. Does

Re: vfs.nfs.iothreads

2012-12-21 Thread Jason McIntyre
On Fri, Dec 21, 2012 at 02:34:50PM +0100, Jan Stary wrote: On 5.2/i386, man sysctl says To adjust the number of kernel nfsio threads used to service asynchronous I/O requests on an NFS client machine: # sysctl vfs.nfs.iothreads=4 The default is 4; 20

Re: vfs.nfs.iothreads

2012-12-21 Thread MichaƂ Markowski
2012/12/21 Jason McIntyre j...@kerhand.co.uk: i get -1 here too. but you;re saying that the value changes to 4 when transferring, right? I found this in /sys/nfs/nfs_vfsops.c: if (nfs_niothreads 0) { nfs_niothreads = 4; nfs_getset_niothreads(1); }