slow nfs read/write from solaris 8 to solaris 10

there is a bug:4852269 which sums up my problem well.

I have a solaris 10 sparc with a big nfs shared raid5, and most of the other suns I have run solaris 8. the access time from sol8 to sol10 is awfull.

Is there some config/patch I can apply to the solaris 10 box?

I have put on the latest 10_Recommended.zip

[334 byte] By [grpoftreesa] at [2007-11-27 5:10:54]
# 1
Is the nfs shared filesystem on ufs or zfs. There are known issues with nfs exporting zfs filesystems.There are workarounds, but they're a bit of a hack.
robert.cohena at 2007-7-12 10:31:09 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 2

it's a ufs filesystem

If it helps, here is my /etc/default/nfs

# ident "@(#)nfs1.1004/09/01 SMI"

#

# Copyright 2004 Sun Microsystems, Inc. All rights reserved.

# Use is subject to license terms.

#

# Sets the maximum number of concurrent connection oriented connections.

# Default is unlimited and is obtained by not setting NFSD_MAX_CONNECTIONS.

# Equivalent to -c.

#NFSD_MAX_CONNECTIONS=

# Set connection queue length for the NFS over a connection-oriented

# transport. The default value is 32 entries.

# Equivalent to -l.

NFSD_LISTEN_BACKLOG=32

# Start NFS daemon over the specified protocol only.

# Equivalent to -p, ALL is equivalent to -a on the nfsd command line.

# Mutually exclusive with NFSD_DEVICE.

NFSD_PROTOCOL=ALL

# Start NFS daemon for the transport specified by the given device only.

# Equivalent to -t.

# Mutually exclusive with setting NFSD_PROTOCOL.

#NFSD_DEVICE=

# Maximum number of concurrent NFS requests.

# Equivalent to last numeric argument on nfsd command line.

NFSD_SERVERS=16

# Set connection queue length for lockd over a connection-oriented transport.

# Default and minimum value is 32.

LOCKD_LISTEN_BACKLOG=32

# Maximum number of concurrent lockd requests.

# Default is 20.

LOCKD_SERVERS=20

# Retransmit Timeout before lockd tries again.

# Default is 5.

LOCKD_RETRANSMIT_TIMEOUT=5

# Grace period in seconds that all clients (both NLM & NFSv4) have to

# reclaim locks after a server reboot. Also controls the NFSv4 lease

# interval.

# Overrides the deprecated setting LOCKD_GRACE_PERIOD.

# Default is 90 seconds.

GRACE_PERIOD=90

# Deprecated.

# As for GRACE_PERIOD, above.

# Default is 90 seconds.

#LOCKD_GRACE_PERIOD=90

# Sets the minimum version of the NFS protocol that will be registered

# and offered by the server. The default is 2.

#NFS_SERVER_VERSMIN=2

# Sets the maximum version of the NFS protocol that will be registered

# and offered by the server. The default is 4.

NFS_SERVER_VERSMAX=2

# Sets the minimum version of the NFS protocol that will be used by

# the NFS client. Can be overridden by the "vers=" NFS mount option.

# The default is 2.

#NFS_CLIENT_VERSMIN=2

# Sets the maximum version of the NFS protocol that will be used by

# the NFS client. Can be overridden by the "vers=" NFS mount option.

# If "vers=" is not specified for an NFS mount, this is the version

# that will be attempted first. The default is 4.

#NFS_CLIENT_VERSMAX=4

# Determines if the NFS version 4 delegation feature will be enabled

# for the server. If it is enabled, the server will attempt to

# provide delegations to the NFS version 4 client. The default is on.

#NFS_SERVER_DELEGATION=on

# Specifies to nfsmapid daemon that it is to override its default

# behavior of using the DNS domain, and that it is to use 'domain' as

# the domain to append to outbound attribute strings, and that it is to

# use 'domain' to compare against inbound attribute strings.

#NFSMAPID_DOMAIN=domain

#

grpoftreesa at 2007-7-12 10:31:09 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 3
You may want to look at NFS_SERVER_VERSMAX=2 - there would be no harm in changing that to 3 or 4: the server would only permit the relevant nfs version to be used, after checking with client. Version 3 has better performance and I think Version 4 does too.
SimonJMa at 2007-7-12 10:31:09 > top of Java-index,Solaris Operating System,Solaris 10 Features...
# 4

One more note:Remember "Secure by default".

We also had awfull performance until we realized that the sol10 server with the sol10 client are connecting via nfs-v4 and kerberos5 enabled. Since we are serving public content (pictures mostly) only via this share we disabled this transport security (encryption/decryption) and are back to normal sol8 nfs-v3 performance now.

Maybe that is of help to some.

jorgweiss2a at 2007-7-12 10:31:09 > top of Java-index,Solaris Operating System,Solaris 10 Features...