Re: optimising nfs and nfsd
- Reply: Rick Macklem : "Re: optimising nfs and nfsd"
- In reply to: Rick Macklem : "Re: optimising nfs and nfsd"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 30 Oct 2023 13:47:26 UTC
Hi Rick, thanks for the info On Sun, 29 Oct 2023, at 20:28, Rick Macklem wrote: > In summary, if you are getting near wire speed and you > are comfortable with your security situation, then there > isn't much else to do. It seems to depend on the nature of the workload. Sometimes wire speed, sometimes half that. And then: 1. some clients - many reads of small files, hardly any writes 2. others - many reads, loads of writes 3. same as {1,2} above, huge files 4. how many clients access at once 5. how many clients of [1] and [2] types access at the same time looking for an all-in-one synthetic tester if there's such a thing. Large single client transfers client to server are wire speed. Not tested much else, (not sure how), except with dd but that's not really a real-world workload. I'll try the things you suggested. what I can report now, on the server, so before nfs is considered: dd if=/dev/urandom of=test-128k.bin bs=128k count=64000 status=progress 8346009600 bytes (8346 MB, 7959 MiB) transferred 59.001s, 141 MB/s dd if=test-128k.bin of=/dev/null bs=128k status=progress 6550061056 bytes (6550 MB, 6247 MiB) transferred 3.007s, 2178 MB/s dd if=/dev/urandom of=test-4k.bin bs=4k count=2048000 status=progress 8301215744 bytes (8301 MB, 7917 MiB) transferred 78.063s, 106 MB/s dd if=test-4k.bin of=/dev/null bs=4k status=progress 7725998080 bytes (7726 MB, 7368 MiB) transferred 10.002s, 772 MB/s dd if=/dev/urandom of=test-512b.bin bs=512 count=16384000 status=progress 8382560256 bytes (8383 MB, 7994 MiB) transferred 208.019s, 40 MB/s dd if=test-512b.bin of=/dev/null bs=512 status=progress 8304610304 bytes (8305 MB, 7920 MiB) transferred 63.062s, 132 MB/s