NFS Optimization: Difference between revisions
Jump to navigation
Jump to search
(New page: ===Server Side=== ====/etc/exports==== <pre>/mnt/raid5 192.168.15.142/32(rw,async,no_root_squash)</pre> async - dramatic throughput increase, but dangerous if a client does not unmount cle...) |
No edit summary |
||
Line 17: | Line 17: | ||
echo 0 > /proc/sys/net/ipv4/tcp_timestamps | echo 0 > /proc/sys/net/ipv4/tcp_timestamps | ||
====TCP Segmentation offload==== | |||
This will take off some of the tcp overhead if your card supports it.. | This will take off some of the tcp overhead if your card supports it.. | ||
<pre># ethtool -K ethN tso on</pre> | <pre># ethtool -K ethN tso on</pre> |
Revision as of 20:18, 5 April 2009
Server Side
/etc/exports
/mnt/raid5 192.168.15.142/32(rw,async,no_root_squash)
async - dramatic throughput increase, but dangerous if a client does not unmount cleanly..
Tuning /etc/sysctl.conf
net.core.rmem_default = 262144 net.core.rmem_max = 262144 # # Increase the fragmented packet queue length net.ipv4.ipfrag_high_thresh = 524288 net.ipv4.ipfrag_low_thresh = 393216
echo 0 > /proc/sys/net/ipv4/tcp_sack echo 0 > /proc/sys/net/ipv4/tcp_timestamps
TCP Segmentation offload
This will take off some of the tcp overhead if your card supports it..
# ethtool -K ethN tso on
Client Side
/etc/fstab
192.168.15.20:/mnt/raid5 /mnt/raid5 nfs rsize=32768,wsize=32768,intr,hard 0 0
[rw]size=32768 - NFSv3 maximum read write size intr - if the mount drops, you'll still be able to ^C out of whatever operation your running hard - hm?