NSS Memory 1

[pagy]

I have 150 6.5 servers in a tree (all at remote sites) and all these servers NSS is using about 120 meg of RAM, which is fine and not causing a problem (as far as I know). However there is one remote site that is in its own tree, 6.5 again, same model server, same RAM and under a similair load to the other servers but NSS uses only 40 MEG of RAM, why would this be the case?

 

[ITsmyfault]

did anyone set the server -uxxxxx flag on boot? This controls how much RAM NSS takes. NSS by default takes most (80%??) of the ram. It will take less if you tell it to. Get a copy of SEG.NLM (current version is 1.7) and it will take a running tally of what memory parameter is appropriate for your individual server. Just load it, let it run for a bit and then from the main screen hit F10.
The program will calculate the proper memory config variable for you. See TID#10091980 I more than doubled my virtual memory cache pool once I made this adjustment (NSS was taking a lot more than it needed..)
Hope this helps. - Joe

 

[pagy]

Thanks Joe,

Do you know where I can get a copy og seg.nlm?, I've searched the novell website but can't find a download anywhere

 

[marvhuffaker]

I think that command only works on NetWare 6.0. On NW6.5, it will cause your server to not load. That switch is not documented very clearly and I've had discussions with Novell Support about it and in my opinion, everybody is very confused.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[ITsmyfault]

The server -uxxxxxx definitely works on 6.5 I'm using it, Novell tech support told me to use it. It made a huge difference in how much mem NSS grabbed. (as reported by seg.nlm)
Luckily, if you're on SP2, you can get the calculated spec from NoRM. That has been added to the TID I posted above.
go into NoRm, the "memory config"-->logical address space--> this gives you the pie which now includes "fragmented" space.. (keep an eye on this!) then click on "tune logical address space" and it will display the appropriate server -u switch. Run this after the box has been up a while though - not after a fresh reboot.
It may not be fixed, but at least we have some tools to work with.

 

[marvhuffaker]

Hey, I'm not trying to argue.. I've seen it work in some places and not in others. Like I said, I've had Novell support tell me to use, and it killed my server. So we backed out of that idea and moved on to other ideas.

Gotta say thanks for the other info about finding stats on actual memory being used by NSS. Good stuff.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[pagy]

thanks guys, haven't applied sp2 yet. Thats about a month away but I'll check that out when we do.

 

[ITsmyfault]

Hi Marvin - I did not mean to sound argumentative. I appologize if I did. I did not know it didn't work sometimes.. I learn something new from you everyday I think! I've never used that setting before the recent problems before frankly. But it did work great here on 6.5 Sp1, and is still working in SP2. My virtual cache went from 980MB or so (out of 2.5GB) up to 2.1GB. That, and we spec'd the TSAFS to 1% of system RAM and a couple other tweaks. The servers are running well and now memory fragmentation does not seem to the issue. Have an SMS/NCSSDK.NLM issue and I don't think Netware likes my McData switches but that's another story for another day!
I was really happy to see that stuff in NoRM about memory..
Thanks! - Joe