Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

nss settings

Status
Not open for further replies.

terry712

Technical User
Oct 1, 2002
2,175
0
0
GB
netware 6 server sp3
latest ip patch ver k
latest nss patch 3c
op lock 1 and 2 set to off
client caching set to off

all volumes nss - one sys , one data , and a mail volume running grpwise
6.51 - server has 2.5 gb ram

nss currently has no switches and users say it's slower than previous server -

i've run nss /cachestats and
cache hits 85%
cache hit users 77%
system 99%
percent of buckets used 38%

all clients 4.83 sp2

should i enable the op locks?
what settings are desired for nss?
assume seperate switches required for grpwise volume
 
some one must have a view

come on marv lets get your opinion

also have another one but it's running a sybase db
 
:)

I've never really had to mess with any NSS settings. However I don't care what anybody says, I will never turn on oplocks or client file caching. I've seen too many people get hurt.

Just an obvservation though, your cache hits look pretty low. I'm running a Groupwise 5.5 system on NetWare 6.5 and the lowest cache hits is at 94% (user). The others are 97 and 99%. Of course, there are 4GB of RAM so it has lots to work with. You may be able to allocate more for caching if that seems to be what is slowing it down. And, when in doubt, add RAM.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Marv,

What types of problems have you seen with oplocks on? Just curious. Thanks!

Jose
 
The most common are problems accessing database type files. If you browse this same forum, you will find plenty of references to it.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
We run all off our servers with the following in the nssstart.cfg in the server .exe folder.

/Cachebalance=60
/ClosedFileCacheSize=100000
/OpenFileHashShift=17
/NameCacheSize=41251

Got these settings while talking to the nss guys at BrainShare.

This did make a differenc for us after we applied them.

You will want to restart the server after you apply the settings.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top